SVISCOM-Lin Knowledge Base for RAID.mib
MIB descriptions:
4: Unexpected disconnect from ServerView RAID Manager
| Severity: | CRITICAL |
| Description: | Unexpected disconnect from ServerView RAID Manager. |
| Summary: | Unexpected disconnect from ServerView RAID Manager (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10013: BBU failed
| Severity: | CRITICAL |
| Description: | BBU failed. |
| Summary: | Adapter %s: BBU failed (Server %s) |
| Note: | Only informational during recalibration process. |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10022: Disk marked offline
| Severity: | CRITICAL |
| Description: | Disk marked offline. |
| Summary: | Adapter %s: Disk (%s) marked offline (Server %s) |
| Note: | Only informational if affected disk was manually set offline otherwise: |
| Resolution: | Proceed with the following steps:
- If offline disk is member of an array initiate a rebuild to the offline disk.
- If problem persists replace affected disk.
|
| go to top | |
10049: Fan in enclosure failed
| Severity: | CRITICAL |
| Description: | Fan in enclosure failed. |
| Summary: | Adapter %s: Fan %s in enclosure %s failed (Server %s) |
| Resolution: | Replace affected fan within the external storage subsystem. |
| go to top | |
10051: Power supply in enclosure failed
| Severity: | CRITICAL |
| Description: | Power supply in enclosure failed. |
| Summary: | Adapter %s: Power supply %s in enclosure %s failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Check the power cable.
- Check the mains voltage.
- Replace affected power supply.
|
| go to top | |
10052: 3.3V power failed for disk
| Severity: | CRITICAL |
| Description: | 3.3V power failed for disk. |
| Summary: | Adapter %s: 3.3V power failed for disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Check whether all cables are correctly connected to the disk backplane connectors.
- Replace affected disk.
|
| go to top | |
10053: 5.0V power failed for disk
| Severity: | CRITICAL |
| Description: | 5.0V power failed for disk. |
| Summary: | Adapter %s: 5.0V power failed for disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Check whether all cables are correctly connected to the disk backplane connectors.
- Replace affected disk.
|
| go to top | |
10054: 12V power failed for disk
| Severity: | CRITICAL |
| Description: | 12V power failed for disk. |
| Summary: | Adapter %s: 12V power failed for disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Check whether all cables are correctly connected to the disk backplane connectors.
- Replace affected disk.
|
| go to top | |
10079: Logical drive failed
| Severity: | CRITICAL |
| Description: | Logical drive failed. |
| Summary: | Adapter %s: Logical drive %s failed (Server %s) |
| Resolution: | Note: Sometimes it is possible to recover without data loss. Further investigation is needed. |
| go to top | |
10154: BBU failed
| Severity: | CRITICAL |
| Description: | BBU failed. |
| Summary: | Adapter %s: BBU failed (Server %s) |
| Note: | Only informational during recalibration process. |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10204: Fatal firmware error
| Severity: | CRITICAL |
| Description: | Fatal firmware error. |
| Summary: | Adapter %s: Fatal firmware error: %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Disconnect AC and wait 30 seconds before reconnect.
|
| go to top | |
10414: State change from operational to failed
| Severity: | CRITICAL |
| Description: | State change from operational to failed. |
| Summary: | Adapter %s: State change on logical drive %s from operational to failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10418: State change from degraded to failed
| Severity: | CRITICAL |
| Description: | State change from degraded to failed. |
| Summary: | Adapter %s: State change on logical drive %s from degraded to failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disks.
- The array has to be recreated. Note: Data loss is probable.
|
| go to top | |
10422: State change from partially degraded to failed
| Severity: | CRITICAL |
| Description: | State change from partially degraded to failed. |
| Summary: | Adapter %s: State change on logical drive %s from partially degraded to failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disks.
- The array has to be recreated. Note: Data loss is probable.
|
| go to top | |
10426: State change from failed to failed
| Severity: | CRITICAL |
| Description: | State change from failed to failed. |
| Summary: | Adapter %s: State change on logical drive %s from failed to failed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10427: State change by user from available to failed
| Severity: | CRITICAL |
| Description: | State change by user from available to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10432: State change by user from failed to failed
| Severity: | CRITICAL |
| Description: | State change by user from failed to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10437: State change by user from hot spare to failed
| Severity: | CRITICAL |
| Description: | State change by user from hot spare to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10442: State change by user from rebuilding to failed
| Severity: | CRITICAL |
| Description: | State change by user from rebuilding to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10447: State change by user from operational to failed
| Severity: | CRITICAL |
| Description: | State change by user from operational to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10451: State change from available to failed
| Severity: | CRITICAL |
| Description: | State change from available to failed. |
| Summary: | Adapter %s: State change on disk (%s) from available to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10456: State change from failed to failed
| Severity: | CRITICAL |
| Description: | State change from failed to failed. |
| Summary: | Adapter %s: State change on disk (%s) from failed to failed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10461: State change from hot spare to failed
| Severity: | CRITICAL |
| Description: | State change from hot spare to failed. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10466: State change from rebuilding to failed
| Severity: | CRITICAL |
| Description: | State change from rebuilding to failed. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10471: State change from operational to failed
| Severity: | CRITICAL |
| Description: | State change from operational to failed. |
| Summary: | Adapter %s: State change on disk (%s) from operational to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10482: Enclosure I/O module not installed
| Severity: | CRITICAL |
| Description: | Enclosure I/O module not installed. |
| Summary: | Adapter %s: Enclosure %s I/O module %s not installed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10490: State change by user from offline to failed
| Severity: | CRITICAL |
| Description: | State change by user from offline to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10500: State change from offline to failed
| Severity: | CRITICAL |
| Description: | State change from offline to failed. |
| Summary: | Adapter %s: State change on disk (%s) from offline to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10526: Adapter missing after reboot
| Severity: | CRITICAL |
| Description: | Adapter missing after reboot. |
| Summary: | Adapter %s: Adapter missing after reboot (Server %s) |
| Note: | Only informational if controller was removed by user otherwise: |
| Resolution: | Proceed with the following steps:
- Unplug affected controller, wait 30 seconds, reinsert it.
- If problem persists replace affected controller.
- If problem persists replace mainboard.
|
| go to top | |
10544: Adapter needs replacement, faulty IOP detected
| Severity: | CRITICAL |
| Description: | Adapter needs replacement, faulty IOP detected. |
| Summary: | Adapter %s: Adapter needs replacement, faulty IOP detected (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10630: Disk failed due to bad block table overflow
| Severity: | CRITICAL |
| Description: | Disk failed due to bad block table overflow. |
| Summary: | Adapter %s: Disk (%s) failed due to bad block table overflow (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10631: Disk failure detected during POST
| Severity: | CRITICAL |
| Description: | Disk failure detected during POST. |
| Summary: | Adapter %s: Disk (%s) failure detected during POST (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10632: Failure detected during POST
| Severity: | CRITICAL |
| Description: | Failure detected during POST. |
| Summary: | Adapter %s: Failure detected during POST (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10633: Multiple failure on disk detected
| Severity: | CRITICAL |
| Description: | Multiple failure on disk detected. |
| Summary: | Adapter %s: Multiple failure on disk (%s) detected, internal info %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10635: Disk failure detected by Patrol Read
| Severity: | CRITICAL |
| Description: | Disk failure detected by Patrol Read. |
| Summary: | Adapter %s: Disk (%s) failure detected by Patrol Read (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10636: Disk failure detected after successfully building redundancy
| Severity: | CRITICAL |
| Description: | Disk failure detected after successfully building redundancy. |
| Summary: | Adapter %s: Disk (%s) failure detected after successfully building redundancy (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10637: Disk failure detected after aborting building redundancy
| Severity: | CRITICAL |
| Description: | Disk failure detected after aborting building redundancy. |
| Summary: | Adapter %s: Disk (%s) failure detected after aborting building redundancy (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10638: Disk failed
| Severity: | CRITICAL |
| Description: | Disk failed. |
| Summary: | Adapter %s: Disk (%s) failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10639: Disk failed
| Severity: | CRITICAL |
| Description: | Disk failed. |
| Summary: | Adapter %s: Disk (%s) failed, internal info %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10688: Multiple failure on disk detected during POST
| Severity: | CRITICAL |
| Description: | Multiple failure on disk detected during POST. |
| Summary: | Adapter %s: Multiple failure on disk (%s) detected during POST, internal info %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10689: Disk failed due to SAS/SATA interface error rate too high
| Severity: | CRITICAL |
| Description: | Disk failed due to SAS/SATA interface error rate too high. |
| Summary: | Adapter %s: Disk (%s) failed due to SAS/SATA interface error rate too high (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10695: Disk failed due to write error detection by driver
| Severity: | CRITICAL |
| Description: | Disk failed due to write error detection by driver. |
| Summary: | Adapter %s: Disk (%s) failed due to write error detection by driver (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10711: Disk failed since it never entered ready state
| Severity: | CRITICAL |
| Description: | Disk failed since it never entered ready state. |
| Summary: | Adapter %s: Disk (%s) failed since it never entered ready state, %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10717: Firmware initialization failed
| Severity: | CRITICAL |
| Description: | Firmware initialization failed. |
| Summary: | Adapter %s: Firmware initialization failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10718: Firmware recovery failed
| Severity: | CRITICAL |
| Description: | Firmware recovery failed. |
| Summary: | Adapter %s: Firmware recovery failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10755: State change from copyback to failed
| Severity: | CRITICAL |
| Description: | State change from copyback to failed. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10763: State change from JBOD to failed
| Severity: | CRITICAL |
| Description: | State change from JBOD to failed. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10781: State change by user from copyback to failed
| Severity: | CRITICAL |
| Description: | State change by user from copyback to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10789: State change by user from JBOD to failed
| Severity: | CRITICAL |
| Description: | State change by user from JBOD to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10903: Logical drive access blocked as cached data in CacheCade is unavailable
| Severity: | CRITICAL |
| Description: | Logical drive access blocked as cached data in CacheCade is unavailable. |
| Summary: | Adapter %s: Logical drive %s access blocked as cached data in CacheCade is unavailable (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10910: Unexpected sense
| Severity: | CRITICAL |
| Description: | Unexpected sense. |
| Summary: | Adapter %s: Unexpected sense: Disk (%s), Key/ASC/ASCQ: %s: %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10925: State change from shielded to failed
| Severity: | CRITICAL |
| Description: | State change from shielded to failed. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10931: State change from shielded to shielded
| Severity: | CRITICAL |
| Description: | State change from shielded to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10932: State change from available to shielded
| Severity: | CRITICAL |
| Description: | State change from available to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from available to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10933: State change from offline to shielded
| Severity: | CRITICAL |
| Description: | State change from offline to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from offline to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10934: State change from failed to shielded
| Severity: | CRITICAL |
| Description: | State change from failed to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from failed to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10935: State change from hot spare to shielded
| Severity: | CRITICAL |
| Description: | State change from hot spare to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10936: State change from rebuilding to shielded
| Severity: | CRITICAL |
| Description: | State change from rebuilding to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10937: State change from operational to shielded
| Severity: | CRITICAL |
| Description: | State change from operational to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from operational to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10938: State change from copyback to shielded
| Severity: | CRITICAL |
| Description: | State change from copyback to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10939: State change from JBOD to shielded
| Severity: | CRITICAL |
| Description: | State change from JBOD to shielded. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10942: State change by user from shielded to failed
| Severity: | CRITICAL |
| Description: | State change by user from shielded to failed. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to failed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10948: State change by user from shielded to shielded
| Severity: | CRITICAL |
| Description: | State change by user from shielded to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to shielded (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10949: State change by user from available to shielded
| Severity: | CRITICAL |
| Description: | State change by user from available to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10950: State change by user from offline to shielded
| Severity: | CRITICAL |
| Description: | State change by user from offline to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10951: State change by user from failed to shielded
| Severity: | CRITICAL |
| Description: | State change by user from failed to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10952: State change by user from hot spare to shielded
| Severity: | CRITICAL |
| Description: | State change by user from hot spare to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10953: State change by user from rebuilding to shielded
| Severity: | CRITICAL |
| Description: | State change by user from rebuilding to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10954: State change by user from operational to shielded
| Severity: | CRITICAL |
| Description: | State change by user from operational to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10955: State change by user from copyback to shielded
| Severity: | CRITICAL |
| Description: | State change by user from copyback to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10956: State change by user from JBOD to shielded
| Severity: | CRITICAL |
| Description: | State change by user from JBOD to shielded. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to shielded (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10957: Internal error
| Severity: | CRITICAL |
| Description: | Internal error. |
| Summary: | Adapter %s: Internal error (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10958: Incompatible PCI slot bandwidth
| Severity: | CRITICAL |
| Description: | Incompatible PCI slot bandwidth. |
| Summary: | Adapter %s: Incompatible PCI slot bandwidth (Server %s) |
| Resolution: | Reinstall adapter in a compatible PCI slot. |
| go to top | |
10962: Temperature above error threshold
| Severity: | CRITICAL |
| Description: | Temperature above error threshold. |
| Summary: | Adapter %s: Temperature above error threshold (Server %s) |
| Resolution: | Increase cooling or reduce write load. |
| go to top | |
10963: Internal voltage out of range
| Severity: | CRITICAL |
| Description: | Internal voltage out of range. |
| Summary: | Adapter %s: Internal voltage out of range (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10964: Auxiliary voltage out of range
| Severity: | CRITICAL |
| Description: | Auxiliary voltage out of range. |
| Summary: | Adapter %s: Auxiliary voltage out of range (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10965: Flashback error
| Severity: | CRITICAL |
| Description: | Flashback error. |
| Summary: | Adapter %s: Flashback error (Server %s) |
| Resolution: | Proceed with the following steps:
- Backup data from affected adapter.
- Replace adapter as soon as possible.
- Restore data.
|
| go to top | |
10966: Non-correctable PCI errors detected
| Severity: | CRITICAL |
| Description: | Non-correctable PCI errors detected. |
| Summary: | Adapter %s: Non-correctable PCI errors detected (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10981: Attach failed
| Severity: | CRITICAL |
| Description: | Attach failed. |
| Summary: | Adapter %s: Attach failed (Server %s) |
| Resolution: | If problem persists, call your local Fujitsu Helpdesk. |
| go to top | |
10984: Detached
| Severity: | CRITICAL |
| Description: | Detached. |
| Summary: | Adapter %s: Detached (Server %s) |
| Resolution: | For information only. |
| go to top | |
11001: Fatal error during boot
| Severity: | CRITICAL |
| Description: | Fatal error during boot. |
| Summary: | Adapter %s: Fatal error during boot - %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
11019: Logical drive access blocked as cached data from peer adapter is unavailable
| Severity: | CRITICAL |
| Description: | Logical drive access blocked as cached data from peer adapter is unavailable. |
| Summary: | Adapter %s: Logical drive %s access blocked as cached data from peer adapter is unavailable (Server %s) |
| Resolution: | For information only. |
| go to top | |
10002: Write access of the ServerView RAID Manager revoked
| Severity: | MINOR |
| Description: | Write access of the ServerView RAID Manager revoked. |
| Summary: | Write access of the ServerView RAID Manager revoked by user %s (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10003: BBU temperature out of range
| Severity: | MAJOR |
| Description: | BBU temperature out of range. |
| Summary: | Adapter %s: BBU temperature out of range (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10004: BBU temperature unstable
| Severity: | MAJOR |
| Description: | BBU temperature unstable. |
| Summary: | Adapter %s: BBU temperature unstable (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10005: BBU temperature above threshold
| Severity: | MAJOR |
| Description: | BBU temperature above threshold. |
| Summary: | Adapter %s: BBU temperature above threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10006: BBU voltage out of range
| Severity: | MAJOR |
| Description: | BBU voltage out of range. |
| Summary: | Adapter %s: BBU voltage out of range (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10007: BBU voltage unstable
| Severity: | MAJOR |
| Description: | BBU voltage unstable. |
| Summary: | Adapter %s: BBU voltage unstable (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10008: BBU voltage below threshold
| Severity: | MAJOR |
| Description: | BBU voltage below threshold. |
| Summary: | Adapter %s: BBU voltage below threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10009: BBU communication error
| Severity: | MAJOR |
| Description: | BBU communication error. |
| Summary: | Adapter %s: BBU communication error (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10014: BBU fast charging failed
| Severity: | MAJOR |
| Description: | BBU fast charging failed. |
| Summary: | Adapter %s: BBU fast charging failed (Server %s) |
| Note: | Do not interrupt the charging process by reboots or shutdowns. |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10015: BBU charge count exceeded
| Severity: | MINOR |
| Description: | BBU charge count exceeded. |
| Summary: | Adapter %s: BBU charge count exceeded (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10016: BBU needs reconditioning
| Severity: | MINOR |
| Description: | BBU needs reconditioning. |
| Summary: | Adapter %s: BBU needs reconditioning (Server %s) |
| Note: | By default BBU recalibration is automatically initiated every 30 days. |
| Resolution: | Proceed with the following steps:
- If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID Manager).
|
| go to top | |
10023: Disk timed out
| Severity: | MAJOR |
| Description: | Disk timed out. |
| Summary: | Adapter %s: Disk (%s) timed out (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10025: Global hot spare deleted on disk
| Severity: | MINOR |
| Description: | Global hot spare deleted on disk. |
| Summary: | Adapter %s: Global hot spare deleted on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10027: Dedicated hot spare deleted on disk
| Severity: | MINOR |
| Description: | Dedicated hot spare deleted on disk. |
| Summary: | Adapter %s: Dedicated hot spare deleted on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10030: Rebuild on disk failed
| Severity: | MAJOR |
| Description: | Rebuild on disk failed. |
| Summary: | Adapter %s: Rebuild on disk (%s) failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10031: Bad block on disk detected
| Severity: | MAJOR |
| Description: | Bad block on disk detected. |
| Summary: | Adapter %s: Bad block on disk (%s) LBA %s detected (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10033: Disk removed
| Severity: | MINOR |
| Description: | Disk removed. |
| Summary: | Adapter %s: Disk (%s) removed (Server %s) |
| Note: | Only informational if affected disk has been removed otherwise: |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10036: Bad sector on disk detected
| Severity: | MAJOR |
| Description: | Bad sector on disk detected. |
| Summary: | Adapter %s: Bad sector on disk (%s) detected (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10037: COD I/O error on disk
| Severity: | MAJOR |
| Description: | COD I/O error on disk. |
| Summary: | Adapter %s: COD I/O error on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a rebuild (e.g. via ServerView RAID Manager) of affected disk.
- If problem persists replace affected disk.
|
| go to top | |
10038: Error on disk detected
| Severity: | MAJOR |
| Description: | Error on disk detected. |
| Summary: | Adapter %s: Error on disk (%s) detected (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10040: Retry I/O on disk
| Severity: | MAJOR |
| Description: | Retry I/O on disk. |
| Summary: | Adapter %s: Retry I/O on disk (%s) (Server %s) |
| Resolution: | If the problem occurs repeatedly replace affected disk. |
| go to top | |
10041: ECC error on disk
| Severity: | MAJOR |
| Description: | ECC error on disk. |
| Summary: | Adapter %s: ECC error on disk (%s) (Server %s) |
| Resolution: | If the problem occurs repeatedly replace affected disk. |
| go to top | |
10043: Media error on disk
| Severity: | MAJOR |
| Description: | Media error on disk. |
| Summary: | Adapter %s: Media error on disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10044: SMART warning on disk
| Severity: | MINOR |
| Description: | SMART warning on disk. |
| Summary: | Adapter %s: SMART warning on disk (%s) (Server %s) |
| Note: | Disk reports a prefailure. The affected disk might fail soon. |
| Resolution: | Proceed with the following steps:
- Replace the disk during next maintenance.
|
| go to top | |
10045: SMART error on disk
| Severity: | MINOR |
| Description: | SMART error on disk. |
| Summary: | Adapter %s: SMART error on disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10046: Bad disk inserted in enclosure
| Severity: | MAJOR |
| Description: | Bad disk inserted in enclosure. |
| Summary: | Adapter %s: Bad disk inserted in enclosure %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10047: Enclosure powered down
| Severity: | MAJOR |
| Description: | Enclosure powered down. |
| Summary: | Adapter %s: Enclosure %s powered down (Server %s) |
| Resolution: | If this error message is not a result of a planned power off of the external storage subsystem:
Proceed with the following steps:
- Check the power cable(s).
- Check the mains voltage.
- Replace affected power supply(s).
|
| go to top | |
10050: Temperature sensor in enclosure above threshold
| Severity: | MAJOR |
| Description: | Temperature sensor in enclosure above threshold. |
| Summary: | Adapter %s: Temperature sensor %s in enclosure %s above threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
|
| go to top | |
10057: Rebuild failed on logical drive
| Severity: | MAJOR |
| Description: | Rebuild failed on logical drive. |
| Summary: | Adapter %s: Rebuild failed on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
|
| go to top | |
10058: Rebuild aborted on logical drive
| Severity: | MINOR |
| Description: | Rebuild aborted on logical drive. |
| Summary: | Adapter %s: Rebuild aborted on logical drive %s (Server %s) |
| Note: | Rebuild was probably aborted by user. Attention: The affected RAID array is still degraded. |
| Resolution: | Proceed with the following steps:
- The rebuild should be started again as soon as possible.
|
| go to top | |
10062: Consistency check failed on logical drive
| Severity: | MAJOR |
| Description: | Consistency check failed on logical drive. |
| Summary: | Adapter %s: Consistency check failed on logical drive %s (Server %s) |
| Resolution: | Failure happens only if a disk out of the logical drive failed.
Proceed with the following steps:
- Check state of logical drive.
- If logical drive is not operational, check state of affected disk.
- Check for additional error messages for affected disk.
|
| go to top | |
10063: Consistency check aborted on logical drive
| Severity: | MINOR |
| Description: | Consistency check aborted on logical drive. |
| Summary: | Adapter %s: Consistency check aborted on logical drive %s (Server %s) |
| Note: | Consistency check was probably aborted by user. |
| Resolution: | Proceed with the following steps:
- The consistency check should be started again as soon as possible.
|
| go to top | |
10066: Consistency check finished with errors on logical drive
| Severity: | MAJOR |
| Description: | Consistency check finished with errors on logical drive. |
| Summary: | Adapter %s: Consistency check finished with errors on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10067: Inconsistency detected on logical drive
| Severity: | MAJOR |
| Description: | Inconsistency detected on logical drive. |
| Summary: | Adapter %s: Inconsistency detected on logical drive %s at LBA %s (Server %s) |
| Resolution: | Check if logical drive is initialized. If initialized check the following:
Proceed with the following steps:
- Backup your data.
- Start a consistency check with fix.
- Compare backup data with data on logical drive.
- If different (data lost), restore last good data.
|
| go to top | |
10070: Migration failed on logical drive
| Severity: | MAJOR |
| Description: | Migration failed on logical drive. |
| Summary: | Adapter %s: Migration failed on logical drive %s (Server %s) |
| Note: | The logical drive is failed (multi dead). |
| Resolution: | Proceed with the following steps:
- Replace broken drives.
- Create new configuration and restore last good data.
|
| go to top | |
10071: Migration aborted on logical drive
| Severity: | MINOR |
| Description: | Migration aborted on logical drive. |
| Summary: | Adapter %s: Migration aborted on logical drive %s (Server %s) |
| Resolution: | Note: Migration was probably aborted by user. For information only. |
| go to top | |
10074: Patrol Read aborted
| Severity: | MINOR |
| Description: | Patrol Read aborted. |
| Summary: | Adapter %s: Patrol Read aborted (Server %s) |
| Resolution: | Note: Patrol read was probably aborted by user. For information only. |
| go to top | |
10078: Logical drive degraded
| Severity: | MAJOR |
| Description: | Logical drive degraded. |
| Summary: | Adapter %s: Logical drive %s degraded (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a rebuild of affected disk (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10081: Logical drive deleted
| Severity: | MINOR |
| Description: | Logical drive deleted. |
| Summary: | Adapter %s: Logical drive %s deleted (Server %s) |
| Resolution: | For information only. |
| go to top | |
10083: Logical drive error on disk
| Severity: | MAJOR |
| Description: | Logical drive error on disk. |
| Summary: | Adapter %s: Logical drive %s: Error on disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10084: Logical drive bad block detected
| Severity: | MAJOR |
| Description: | Logical drive bad block detected. |
| Summary: | Adapter %s: Logical drive %s: Bad block at LBA %s detected (Server %s) |
| Resolution: | Proceed with the following steps:
- Try to rewrite data.
- If problem persists replace affected disk.
|
| go to top | |
10089: BGI canceled on logical drive
| Severity: | MINOR |
| Description: | BGI canceled on logical drive. |
| Summary: | Adapter %s: BGI canceled on logical drive %s (Server %s) |
| Resolution: | Background initialization (BGI) resumes automatically after a certain period of time. For information only. |
| go to top | |
10090: Initialization canceled on logical drive
| Severity: | MINOR |
| Description: | Initialization canceled on logical drive. |
| Summary: | Adapter %s: Initialization canceled on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10093: Hot spare operation on logical drive failed
| Severity: | MAJOR |
| Description: | Hot spare operation on logical drive failed. |
| Summary: | Adapter %s: Hot spare operation on logical drive %s failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Replace affected disk.
|
| go to top | |
10094: Logical drive forced from failed to degraded
| Severity: | MAJOR |
| Description: | Logical drive forced from failed to degraded. |
| Summary: | Adapter %s: Logical drive %s forced from failed to degraded (Server %s) |
| Resolution: | Proceed with the following steps:
- Temporary offline case.
- Try to rebuild remaining defect drive.
|
| go to top | |
10096: Alarm disabled
| Severity: | MINOR |
| Description: | Alarm disabled. |
| Summary: | Adapter %s: Alarm disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10139: Channel disabled
| Severity: | MINOR |
| Description: | Channel disabled. |
| Summary: | Adapter %s: Channel %s disabled (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10151: BBU voltage problem detected
| Severity: | MAJOR |
| Description: | BBU voltage problem detected. |
| Summary: | Adapter %s: BBU voltage problem detected (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10152: BBU temperature problem detected
| Severity: | MAJOR |
| Description: | BBU temperature problem detected. |
| Summary: | Adapter %s: BBU temperature problem detected (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10157: Disk error fixed
| Severity: | MINOR |
| Description: | Disk error fixed. |
| Summary: | Adapter %s: Disk error fixed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10170: Reboot required
| Severity: | MAJOR |
| Description: | Reboot required. |
| Summary: | Reboot required (Server %s) |
| Resolution: | For information only. |
| go to top | |
10195: Unable to recover cache data from TBBU
| Severity: | MAJOR |
| Description: | Unable to recover cache data from TBBU. |
| Summary: | Adapter %s: Unable to recover cache data from TBBU (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10197: Cluster down; communication with peer lost
| Severity: | MAJOR |
| Description: | Cluster down; communication with peer lost. |
| Summary: | Adapter %s: Cluster down; communication with peer lost (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10200: Controller cache discarded
| Severity: | MAJOR |
| Description: | Controller cache discarded. |
| Summary: | Adapter %s: Adapter cache discarded due to memory/BBU problems (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10201: Unable to recover cache data
| Severity: | MAJOR |
| Description: | Unable to recover cache data. |
| Summary: | Adapter %s: Unable to recover cache data due to configuration mismatch (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10203: Controller cache discarded
| Severity: | MAJOR |
| Description: | Controller cache discarded. |
| Summary: | Adapter %s: Adapter cache discarded due to firmware version IOncompatibility (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10206: Flash downloaded image corrupt
| Severity: | MAJOR |
| Description: | Flash downloaded image corrupt. |
| Summary: | Adapter %s: Flash downloaded image corrupt (Server %s) |
| Resolution: | Proceed with the following steps:
- Download again.
- Retry flash.
|
| go to top | |
10207: Flash erase error
| Severity: | MAJOR |
| Description: | Flash erase error. |
| Summary: | Adapter %s: Flash erase error (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10208: Flash timeout during erase
| Severity: | MAJOR |
| Description: | Flash timeout during erase. |
| Summary: | Adapter %s: Flash timeout during erase (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10209: Flash error
| Severity: | MAJOR |
| Description: | Flash error. |
| Summary: | Adapter %s: Flash error (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10212: Flash programming error
| Severity: | MAJOR |
| Description: | Flash programming error. |
| Summary: | Adapter %s: Flash programming error (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10213: Flash timeout during programming
| Severity: | MAJOR |
| Description: | Flash timeout during programming. |
| Summary: | Adapter %s: Flash timeout during programming (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10214: Flash chip type unknown
| Severity: | MINOR |
| Description: | Flash chip type unknown. |
| Summary: | Adapter %s: Flash chip type unknown (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10215: Flash command set unknown
| Severity: | MAJOR |
| Description: | Flash command set unknown. |
| Summary: | Adapter %s: Flash command set unknown (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10216: Flash verify failure
| Severity: | MAJOR |
| Description: | Flash verify failure. |
| Summary: | Adapter %s: Flash verification failure (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10221: Multi-bit ECC error
| Severity: | MAJOR |
| Description: | Multi-bit ECC error. |
| Summary: | Adapter %s: Multi-bit ECC error: ECAR=%s, ELOG=%s, (%s) (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the RAID controller DIMM module (cache). |
| go to top | |
10222: Single-bit ECC error
| Severity: | MAJOR |
| Description: | Single-bit ECC error. |
| Summary: | Adapter %s: Single-bit ECC error: ECAR=%s, ELOG=%s, (%s) (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the RAID controller DIMM module (cache). |
| go to top | |
10223: Not enough controller memory
| Severity: | MAJOR |
| Description: | Not enough controller memory. |
| Summary: | Adapter %s: Not enough adapter memory (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10231: BGI finished with uncorrectable errors
| Severity: | MAJOR |
| Description: | BGI finished with uncorrectable errors. |
| Summary: | Adapter %s: BGI finished with uncorrectable errors on logical drive %s (Server %s) |
| Resolution: | Initiate consistency check (e.g. via ServerView RAID Manager). |
| go to top | |
10232: BGI detected uncorrectable double medium errors
| Severity: | MAJOR |
| Description: | BGI detected uncorrectable double medium errors. |
| Summary: | Adapter %s: BGI detected uncorrectable multiple medium errors (disk (%s) at LBA %s on logical drive %s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10233: BGI failed
| Severity: | MAJOR |
| Description: | BGI failed. |
| Summary: | Adapter %s: BGI failed on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Restart Background initialization (BGI).
- Replace affected disk.
|
| go to top | |
10237: Consistency check found inconsistent parity
| Severity: | MAJOR |
| Description: | Consistency check found inconsistent parity. |
| Summary: | Adapter %s: Consistency check found inconsistent parity on logical drive %s at stripe %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Start consistency check again.
- If problem persists backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10240: Initialization failed
| Severity: | MAJOR |
| Description: | Initialization failed. |
| Summary: | Adapter %s: Initialization failed on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Start initialization again.
|
| go to top | |
10245: Reconstruct detected uncorrectable double medium errors
| Severity: | MAJOR |
| Description: | Reconstruct detected uncorrectable double medium errors. |
| Summary: | Adapter %s: Migration detected uncorrectable multiple medium errors (logical drive %s at LBA %s on disk (%s) at LBA %s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10248: Reconstruction resume failed
| Severity: | MAJOR |
| Description: | Reconstruction resume failed. |
| Summary: | Adapter %s: Resume migration of logical drive %s failed due to Configuration Mismatch (Server %s) |
| Resolution: | Proceed with the following steps:
- Check the RAID configuration and the event log for additional information.
- Backup data from affected logical drive.
|
| go to top | |
10250: Clear aborted
| Severity: | MINOR |
| Description: | Clear aborted. |
| Summary: | Adapter %s: Clear aborted on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10251: Clear failed
| Severity: | MAJOR |
| Description: | Clear failed. |
| Summary: | Adapter %s: Clear failed on disk (%s) (error %s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
- Verify that current RAID controller drivers are installed.
- Disconnect AC and wait 30 seconds before reconnect.
|
| go to top | |
10255: Error on disk
| Severity: | MAJOR |
| Description: | Error on disk. |
| Summary: | Adapter %s: Error on disk (%s) (error %s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10258: Hot spare SMART polling failed
| Severity: | MAJOR |
| Description: | Hot spare SMART polling failed. |
| Summary: | Adapter %s: Hot spare SMART polling failed on disk (%s) (error %s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10259: Disk not supported
| Severity: | MAJOR |
| Description: | Disk not supported. |
| Summary: | Adapter %s: Disk (%s) is not supported (Server %s) |
| Resolution: | Install supported disk. |
| go to top | |
10262: Patrol Read found an uncorrectable medium error
| Severity: | MAJOR |
| Description: | Patrol Read found an uncorrectable medium error. |
| Summary: | Adapter %s: Patrol Read found an uncorrectable medium error on disk (%s) at LBA %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10263: Predictive failure
| Severity: | MINOR |
| Description: | Predictive failure. |
| Summary: | Adapter %s: Predictive failure: Disk (%s) (Server %s) |
| Note: | Disk reports a prefailure. The affected disk might fail soon. |
| Resolution: | Proceed with the following steps:
- Replace the disk during next maintenance.
|
| go to top | |
10264: Puncturing bad block
| Severity: | MAJOR |
| Description: | Puncturing bad block. |
| Summary: | Adapter %s: Puncturing bad block on disk (%s) at LBA %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10265: Rebuild aborted by user
| Severity: | MINOR |
| Description: | Rebuild aborted by user. |
| Summary: | Adapter %s: Rebuild aborted by user on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10271: Rebuild stopped
| Severity: | MAJOR |
| Description: | Rebuild stopped. |
| Summary: | Adapter %s: Rebuild stopped on disk (%s) due to loss of cluster ownership (Server %s) |
| Resolution: | Proceed with the following steps:
|
| go to top | |
10272: Reassign write operation failed
| Severity: | MAJOR |
| Description: | Reassign write operation failed. |
| Summary: | Adapter %s: Reassign write operation failed on disk (%s) at LBA %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10273: Unrecoverable medium error during rebuild
| Severity: | MAJOR |
| Description: | Unrecoverable medium error during rebuild. |
| Summary: | Adapter %s: Unrecoverable medium error during rebuild on disk (%s) at LBA %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10275: Unrecoverable medium error during recovery
| Severity: | MAJOR |
| Description: | Unrecoverable medium error during recovery. |
| Summary: | Adapter %s: Unrecoverable medium error during recovery on disk (%s) at LBA %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10279: Redundant path broken
| Severity: | MAJOR |
| Description: | Redundant path broken. |
| Summary: | Adapter %s: Redundant path to disk (%s) broken (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10281: Dedicated hot spare no longer useful
| Severity: | MINOR |
| Description: | Dedicated hot spare no longer useful. |
| Summary: | Adapter %s: Dedicated hot spare (%s) no longer useful due to deleted array (Server %s) |
| Resolution: | For information only. |
| go to top | |
10282: SAS topology error: Loop detected
| Severity: | MAJOR |
| Description: | SAS topology error: Loop detected. |
| Summary: | Adapter %s: SAS topology error: Loop detected (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10283: SAS topology error: Unaddressable device
| Severity: | MAJOR |
| Description: | SAS topology error: Unaddressable device. |
| Summary: | Adapter %s: SAS topology error: Unaddressable device (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10284: SAS topology error: Multiple ports to the same SAS address
| Severity: | MAJOR |
| Description: | SAS topology error: Multiple ports to the same SAS address. |
| Summary: | Adapter %s: SAS topology error: Multiple ports to the same SAS address (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10285: SAS topology error: Expander error
| Severity: | MAJOR |
| Description: | SAS topology error: Expander error. |
| Summary: | Adapter %s: SAS topology error: Expander error (Server %s) |
| Resolution: | Proceed with the following steps:
- Check the SAS configuration and cabling.
- If problem persists replace affected backplane.
|
| go to top | |
10286: SAS topology error: SMP timeout
| Severity: | MAJOR |
| Description: | SAS topology error: SMP timeout. |
| Summary: | Adapter %s: SAS topology error: SMP timeout (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10287: SAS topology error: Out of route entries
| Severity: | MAJOR |
| Description: | SAS topology error: Out of route entries. |
| Summary: | Adapter %s: SAS topology error: Out of route entries (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10288: SAS topology error: Index not found
| Severity: | MAJOR |
| Description: | SAS topology error: Index not found. |
| Summary: | Adapter %s: SAS topology error: Index not found (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10289: SAS topology error: SMP function failed
| Severity: | MAJOR |
| Description: | SAS topology error: SMP function failed. |
| Summary: | Adapter %s: SAS topology error: SMP function failed (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10290: SAS topology error: SMP CRC error
| Severity: | MAJOR |
| Description: | SAS topology error: SMP CRC error. |
| Summary: | Adapter %s: SAS topology error: SMP CRC error (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10291: SAS topology error: Multiple subtractive
| Severity: | MAJOR |
| Description: | SAS topology error: Multiple subtractive. |
| Summary: | Adapter %s: SAS topology error: Multiple subtractive (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10292: SAS topology error: Table to table
| Severity: | MAJOR |
| Description: | SAS topology error: Table to table. |
| Summary: | Adapter %s: SAS topology error: Table to table (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10293: SAS topology error: Multiple paths
| Severity: | MAJOR |
| Description: | SAS topology error: Multiple paths. |
| Summary: | Adapter %s: SAS topology error: Multiple paths (Server %s) |
| Resolution: | Check the SAS configuration and cabling. |
| go to top | |
10294: Unable to access disk
| Severity: | MAJOR |
| Description: | Unable to access disk. |
| Summary: | Adapter %s: Unable to access disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Replace affected disk.
- Replace affected backplane.
|
| go to top | |
10295: Dedicated hot spare not useful for all arrays
| Severity: | MINOR |
| Description: | Dedicated hot spare not useful for all arrays. |
| Summary: | Adapter %s: Dedicated hot spare not useful for all arrays (Server %s) |
| Resolution: | For information only. |
| go to top | |
10296: Global hot spare does not cover all arrays
| Severity: | MINOR |
| Description: | Global hot spare does not cover all arrays. |
| Summary: | Adapter %s: Global hot spare does not cover all arrays (Server %s) |
| Resolution: | Note: The size of the global hot spare is not sufficient to secure all arrays. |
| go to top | |
10297: Marking inconsistent
| Severity: | MINOR |
| Description: | Marking inconsistent. |
| Summary: | Adapter %s: Marking logical drive %s inconsistent due to active writes at shutdown (Server %s) |
| Resolution: | Initiate consistency check (e.g. via ServerView RAID Manager). |
| go to top | |
10303: BBU needs replacement
| Severity: | MAJOR |
| Description: | BBU has failed and cannot support data retention. |
| Summary: | Adapter %s: BBU has failed and cannot support data retention (Server %s) |
| Resolution: | If the error message occurs right after replacement of the BBU it can be safely ignored. The situation can occur due to the insufficient BBU charge. If the error message occurs during regular operation replace the BBU. |
| go to top | |
10307: BBU relearn timed out
| Severity: | MINOR |
| Description: | BBU relearn timed out. |
| Summary: | Adapter %s: BBU relearn timed out (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10314: BBU removed
| Severity: | MINOR |
| Description: | BBU removed. |
| Summary: | Adapter %s: BBU removed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10317: Enclosure communication lost
| Severity: | MINOR |
| Description: | Enclosure communication lost. |
| Summary: | Adapter %s: Enclosure %s communication lost (Server %s) |
| Resolution: | Proceed with the following steps:
- Check data cable(s) to enclosure.
- Check if enclosure is running.
|
| go to top | |
10320: Enclosure fan removed
| Severity: | MINOR |
| Description: | Enclosure fan removed. |
| Summary: | Adapter %s: Enclosure %s fan %s removed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10321: Enclosure I/O module failed
| Severity: | MAJOR |
| Description: | Enclosure I/O module failed. |
| Summary: | Adapter %s: Enclosure %s I/O module %s failed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10323: Enclosure I/O module removed
| Severity: | MAJOR |
| Description: | Enclosure I/O module removed. |
| Summary: | Adapter %s: Enclosure %s I/O module %s removed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10324: Enclosure shutdown
| Severity: | MAJOR |
| Description: | Enclosure shutdown. |
| Summary: | Adapter %s: Enclosure %s shutdown (Server %s) |
| Resolution: | For information only. |
| go to top | |
10325: Enclosure not supported; too many enclosures connected to port
| Severity: | MINOR |
| Description: | Enclosure not supported; too many enclosures connected to port. |
| Summary: | Adapter %s: Enclosure %s not supported; too many enclosures connected to port (Server %s) |
| Resolution: | Check your enclosure configuration. |
| go to top | |
10326: Enclosure firmware mismatch
| Severity: | MAJOR |
| Description: | Enclosure firmware mismatch. |
| Summary: | Adapter %s: Enclosure %s firmware mismatch (I/O module %s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10327: Enclosure sensor bad
| Severity: | MAJOR |
| Description: | Enclosure sensor bad. |
| Summary: | Adapter %s: Enclosure %s sensor %s bad (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10328: Enclosure PHY bad
| Severity: | MAJOR |
| Description: | Enclosure PHY bad. |
| Summary: | Adapter %s: Enclosure %s PHY bad for slot %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10329: Enclosure is unstable
| Severity: | MAJOR |
| Description: | Enclosure is unstable. |
| Summary: | Adapter %s: Enclosure %s is unstable (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10330: Enclosure hardware error
| Severity: | MAJOR |
| Description: | Enclosure hardware error. |
| Summary: | Adapter %s: Enclosure %s hardware error (Server %s) |
| Resolution: | Proceed with the following steps:
- Check data cable(s) to enclosure.
- Check if enclosure is running.
|
| go to top | |
10331: Enclosure not responding
| Severity: | MAJOR |
| Description: | Enclosure not responding. |
| Summary: | Adapter %s: Enclosure %s not responding (Server %s) |
| Resolution: | Proceed with the following steps:
- Check data cable(s) to enclosure.
- Check if enclosure is running.
|
| go to top | |
10332: SAS/SATA mixing not supported in enclosure
| Severity: | MINOR |
| Description: | SAS/SATA mixing not supported in enclosure. |
| Summary: | Adapter %s: SAS/SATA mixing not supported in enclosure; %s disabled (Server %s) |
| Resolution: | Check your disk configuration within enclosure. |
| go to top | |
10336: Disk too small to be used for auto-rebuild
| Severity: | MINOR |
| Description: | Disk too small to be used for auto-rebuild. |
| Summary: | Adapter %s: Disk (%s) too small to be used for auto rebuild (Server %s) |
| Resolution: | Check your disk configuration. |
| go to top | |
10338: BBU disabled; changing Write-back virtual disks to Write-through
| Severity: | MINOR |
| Description: | BBU disabled; changing Write-back virtual disks to Write-through. |
| Summary: | Adapter %s: BBU disabled; changing Write-back logical drives to Write-through (Server %s) |
| Note: | Only informational during recalibration process. |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10340: Bad block table full
| Severity: | MAJOR |
| Description: | Bad block table full |
| Summary: | Adapter %s: Bad block table on disk (%s) is full; unable to log Block %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10341: MDC aborted due to ownership loss
| Severity: | MINOR |
| Description: | MDC aborted due to ownership loss. |
| Summary: | Adapter %s: MDC aborted due to ownership loss on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Restart consistency check (MDC).
|
| go to top | |
10342: BGI aborted
| Severity: | MINOR |
| Description: | BGI aborted. |
| Summary: | Adapter %s: BGI aborted due to ownership loss on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Restart Background initialization (BGI).
|
| go to top | |
10343: BBU/charger problems detected
| Severity: | MAJOR |
| Description: | BBU/charger problems detected. |
| Summary: | Adapter %s: BBU/charger problems detected; SOH bad (Server %s) |
| Resolution: | Replace the BBU. |
| go to top | |
10344: Single-bit ECC error; warning threshold exceeded
| Severity: | MINOR |
| Description: | Single-bit ECC error; warning threshold exceeded. |
| Summary: | Adapter %s: Single-bit ECC error: ECAR=%s, ELOG=%s, (%s); warning threshold exceeded (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the RAID controller DIMM module (cache). |
| go to top | |
10345: Single-bit ECC error; critical threshold exceeded
| Severity: | MAJOR |
| Description: | Single-bit ECC error; critical threshold exceeded. |
| Summary: | Adapter %s: Single-bit ECC error: ECAR=%s, ELOG=%s, (%s); critical threshold exceeded (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10346: Single-bit ECC error: further reporting disabled
| Severity: | MAJOR |
| Description: | Single-bit ECC error: further reporting disabled. |
| Summary: | Adapter %s: Single-bit ECC error: ECAR=%s, ELOG=%s, (%s); further reporting disabled (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10347: Enclosure power supply cable removed
| Severity: | MINOR |
| Description: | Enclosure power supply cable removed. |
| Summary: | Adapter %s: Enclosure %s power supply %s cable removed (Server %s) |
| Resolution: | Check the enclosure power cable(s). |
| go to top | |
10352: BBU retention test failed
| Severity: | MAJOR |
| Description: | BBU retention test failed. |
| Summary: | Adapter %s: BBU retention test failed (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10355: NVRAM retention test failed
| Severity: | MAJOR |
| Description: | NVRAM retention test failed. |
| Summary: | Adapter %s: NVRAM retention test failed (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10357: Self check test failed
| Severity: | MAJOR |
| Description: | Self check test failed. |
| Summary: | Adapter %s: %s test failed on %s pass. fail data: errorOffset=%s goodData=%s badData=%s (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10362: NVRAM is corrupt; reinitializing
| Severity: | MINOR |
| Description: | NVRAM is corrupt; reinitializing. |
| Summary: | Adapter %s: NVRAM is corrupt; reinitializing (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the RAID controller. |
| go to top | |
10363: NVRAM mismatch occurred
| Severity: | MINOR |
| Description: | NVRAM mismatch occurred. |
| Summary: | Adapter %s: NVRAM mismatch occurred (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the RAID controller. |
| go to top | |
10364: SAS wide port lost link on PHY
| Severity: | MINOR |
| Description: | SAS wide port lost link on PHY. |
| Summary: | Adapter %s: SAS wide port %s lost link on PHY %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10366: SAS port has exceeded the allowed error rate
| Severity: | MINOR |
| Description: | SAS port has exceeded the allowed error rate. |
| Summary: | Adapter %s: SAS port %s, PHY %s has exceeded the allowed error rate (Server %s) |
| Note: | Disk reports errors. The affected disk might fail soon. |
| Resolution: | Proceed with the following steps:
- Replace the disk as soon as possible.
|
| go to top | |
10367: Bad block reassigned
| Severity: | MINOR |
| Description: | Bad block reassigned. |
| Summary: | Adapter %s: Bad block reassigned on disk (%s) from LBA %s to LBA %s (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the disk during next maintenance. |
| go to top | |
10376: Enclosure firmware download failed
| Severity: | MAJOR |
| Description: | Enclosure firmware download failed. |
| Summary: | Adapter %s: Enclosure %s firmware download failed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10377: Disk is not certified
| Severity: | MINOR |
| Description: | Disk is not certified. |
| Summary: | Adapter %s: Disk (%s) is not certified (Server %s) |
| Resolution: | Check the type of your disk. |
| go to top | |
10378: Dirty cache data discarded by user
| Severity: | MINOR |
| Description: | Dirty cache data discarded by user. |
| Summary: | Adapter %s: Dirty cache data discarded by user (Server %s) |
| Resolution: | For information only. |
| go to top | |
10379: PDs missing from configuration at boot
| Severity: | MINOR |
| Description: | PDs missing from configuration at boot. |
| Summary: | Adapter %s: Disks missing from configuration at boot (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10380: VDs missing drives and will go offline at boot
| Severity: | MINOR |
| Description: | VDs missing drives and will go offline at boot. |
| Summary: | Adapter %s: Logical drives missing drives and will go offline at boot: %s (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10381: VDs missing at boot
| Severity: | MINOR |
| Description: | VDs missing at boot. |
| Summary: | Adapter %s: Logical drives missing at boot: %s (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10382: Previous configuration completely missing at boot
| Severity: | MINOR |
| Description: | Previous configuration completely missing at boot. |
| Summary: | Adapter %s: Previous configuration completely missing at boot (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10388: Logical drive is partially degraded
| Severity: | MINOR |
| Description: | Logical drive is partially degraded. |
| Summary: | Adapter %s: Logical drive %s partially degraded (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10389: BBU requires reconditioning
| Severity: | MINOR |
| Description: | BBU requires reconditioning. |
| Summary: | Adapter %s: BBU requires reconditioning; please initiate a LEARN cycle (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10398: MDC finished with errors on logical drive
| Severity: | MAJOR |
| Description: | MDC finished with errors on logical drive. |
| Summary: | Adapter %s: MDC finished with errors on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists replace affected disk.
|
| go to top | |
10401: Logical drive disabled because SAS drives not supported
| Severity: | MINOR |
| Description: | Logical drive disabled because SAS drives not supported. |
| Summary: | Adapter %s: Logical drive %s disabled because SAS drives are not supported by this RAID key (Server %s) |
| Resolution: | Check the disks. |
| go to top | |
10402: Disks missing
| Severity: | MINOR |
| Description: | Disks missing. |
| Summary: | Adapter %s: Disks missing (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10408: MDC failed on logical drive
| Severity: | MAJOR |
| Description: | MDC failed on logical drive. |
| Summary: | Adapter %s: MDC failed on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists replace affected disk.
|
| go to top | |
10409: MDC aborted on logical drive
| Severity: | MINOR |
| Description: | MDC aborted on logical drive. |
| Summary: | Adapter %s: MDC aborted on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10412: State change from operational to degraded
| Severity: | MAJOR |
| Description: | State change from operational to degraded. |
| Summary: | Adapter %s: State change on logical drive %s from operational to degraded (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10413: State change from operational to partially degraded
| Severity: | MINOR |
| Description: | State change from operational to partially degraded. |
| Summary: | Adapter %s: State change on logical drive %s from operational to partially degraded (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10416: State change from degraded to degraded
| Severity: | MINOR |
| Description: | State change from degraded to degraded. |
| Summary: | Adapter %s: State change on logical drive %s from degraded to degraded (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10417: State change from degraded to partially degraded
| Severity: | MINOR |
| Description: | State change from degraded to partially degraded. |
| Summary: | Adapter %s: State change on logical drive %s from degraded to partially degraded (Server %s) |
| Resolution: | For information only. |
| go to top | |
10420: State change from partially degraded to degraded
| Severity: | MINOR |
| Description: | State change from partially degraded to degraded. |
| Summary: | Adapter %s: State change on logical drive %s from partially degraded to degraded (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10421: State change from partially degraded to partially degraded
| Severity: | MINOR |
| Description: | State change from partially degraded to partially degraded. |
| Summary: | Adapter %s: State change on logical drive %s from partially degraded to partially degraded (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10424: State change from failed to degraded
| Severity: | MINOR |
| Description: | State change from failed to degraded. |
| Summary: | Adapter %s: State change on logical drive %s from failed to degraded (Server %s) |
| Resolution: | For information only. |
| go to top | |
10425: State change from failed to partially degraded
| Severity: | MINOR |
| Description: | State change from failed to partially degraded. |
| Summary: | Adapter %s: State change on logical drive %s from failed to partially degraded (Server %s) |
| Resolution: | For information only. |
| go to top | |
10475: MDC detected uncorrectable multiple medium errors on logical drive
| Severity: | MAJOR |
| Description: | MDC detected uncorrectable multiple medium errors on logical drive. |
| Summary: | Adapter %s: MDC detected uncorrectable multiple medium errors (disk (%s) at LBA %s on logical drive %s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10476: Disk missing after reboot
| Severity: | MAJOR |
| Description: | Disk missing after reboot. |
| Summary: | Adapter %s: Disk (%s) missing after reboot (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10477: Logical drive missing after reboot
| Severity: | MAJOR |
| Description: | Logical drive missing after reboot. |
| Summary: | Adapter %s: Logical drive %s missing after reboot (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10480: Puncture enabled
| Severity: | MAJOR |
| Description: | Puncture enabled. |
| Summary: | Adapter %s: Puncturing of LBAs enabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10481: Puncture disabled
| Severity: | MAJOR |
| Description: | Puncture disabled. |
| Summary: | Adapter %s: Puncturing of LBAs disabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10485: State change from available to offline
| Severity: | MINOR |
| Description: | State change from available to offline. |
| Summary: | Adapter %s: State change on disk (%s) from available to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10486: State change by user from available to offline
| Severity: | MINOR |
| Description: | State change by user from available to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10487: State change by user from failed to offline
| Severity: | MINOR |
| Description: | State change by user from failed to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10488: State change by user from hot spare to offline
| Severity: | MINOR |
| Description: | State change by user from hot spare to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10492: State change by user from offline to offline
| Severity: | MINOR |
| Description: | State change by user from offline to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10495: State change by user from operational to offline
| Severity: | MINOR |
| Description: | State change by user from operational to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10496: State change by user from rebuilding to offline
| Severity: | MINOR |
| Description: | State change by user from rebuilding to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10497: State change from failed to offline
| Severity: | MINOR |
| Description: | State change from failed to offline. |
| Summary: | Adapter %s: State change on disk (%s) from failed to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10498: State change from hot spare to offline
| Severity: | MINOR |
| Description: | State change from hot spare to offline. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to offline (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually set the disk to hot spare again (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10502: State change from offline to offline
| Severity: | MINOR |
| Description: | State change from offline to offline. |
| Summary: | Adapter %s: State change on disk (%s) from offline to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10505: State change from operational to offline
| Severity: | MINOR |
| Description: | State change from operational to offline. |
| Summary: | Adapter %s: State change on disk (%s) from operational to offline (Server %s) |
| Note: | Only informational if status change was forced by user otherwise: |
| Resolution: | Proceed with the following steps:
|
| go to top | |
10506: State change from rebuilding to offline
| Severity: | MINOR |
| Description: | State change from rebuilding to offline. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to offline (Server %s) |
| Note: | Only informational if status change was forced by user otherwise: |
| Resolution: | Proceed with the following steps:
|
| go to top | |
10508: Data in cache not flushed during power up
| Severity: | MAJOR |
| Description: | Data in cache not flushed during power up. |
| Summary: | Adapter %s: Data in cache not flushed during power up (Server %s) |
| Resolution: | If the problem occurs repeatedly call your local Fujitsu Helpdesk. |
| go to top | |
10512: Logical drive error on disk media
| Severity: | MAJOR |
| Description: | Logical drive error on disk media. |
| Summary: | Adapter %s: Logical drive %s: Error on disk %s %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10514: Consistency check finished with errors on logical drive
| Severity: | MAJOR |
| Description: | Consistency check finished with errors on logical drive. |
| Summary: | Adapter %s: Consistency check finished with errors on logical drive %s: %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10515: Error on logical drive detected
| Severity: | MAJOR |
| Description: | Error on logical drive detected. |
| Summary: | Adapter %s: Error on logical drive %s detected (Server %s) |
| Resolution: | Proceed with the following steps:
- Check/replace cable between controller and affected disk.
- If problem persists replace disk.
|
| go to top | |
10516: Disk forced from failed to online
| Severity: | MAJOR |
| Description: | Disk forced from failed to online. |
| Summary: | Adapter %s: Disk (%s) forced from failed to online (Server %s) |
| Resolution: | For information only. |
| go to top | |
10517: Transfer speed of disk changed
| Severity: | MINOR |
| Description: | Transfer speed of disk changed. |
| Summary: | Adapter %s: Transfer speed of disk (%s) changed (Server %s) |
| Resolution: | Proceed with the following steps:
- Check/replace cable between controller and affected disk.
- If problem persists replace disk.
|
| go to top | |
10518: SAS port lost link
| Severity: | MAJOR |
| Description: | SAS port lost link. |
| Summary: | Adapter %s: SAS port %s lost link (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10522: Global affinity hot spare commissioned in a different enclosure
| Severity: | MINOR |
| Description: | Global affinity hot spare commissioned in a different enclosure. |
| Summary: | Adapter %s: Global affinity hot spare (%s) commissioned in a different enclosure (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10523: Foreign configuration table overflow
| Severity: | MINOR |
| Description: | Foreign configuration table overflow. |
| Summary: | Adapter %s: Foreign configuration table overflow (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10524: Partial foreign configuration imported
| Severity: | MINOR |
| Description: | Partial foreign configuration imported. |
| Summary: | Adapter %s: Partial foreign configuration imported, disks not imported (device numbers): %s (Server %s) |
| Note: | Only parts of your config were imported. |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10528: Rebuild aborted on disk
| Severity: | MINOR |
| Description: | Rebuild aborted on disk. |
| Summary: | Adapter %s: Rebuild aborted on disk (%s) (Server %s) |
| Note: | Only informational if rebuild was aborted by user otherwise: |
| Resolution: | Proceed with the following steps:
- Initiate a rebuild again (e.g. via ServerView RAID Manager).
|
| go to top | |
10529: Consistency check finished with correctable errors on logical drive
| Severity: | MAJOR |
| Description: | Consistency check finished with correctable errors on logical drive. |
| Summary: | Adapter %s: Consistency check finished with %s correctable errors on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10530: Consistency check finished with uncorrectable errors on logical drive
| Severity: | MAJOR |
| Description: | Consistency check finished with uncorrectable errors on logical drive. |
| Summary: | Adapter %s: Consistency check finished with %s uncorrectable errors on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10532: MDC finished with uncorrectable errors on logical drive
| Severity: | MAJOR |
| Description: | MDC finished with uncorrectable errors on logical drive. |
| Summary: | Adapter %s: MDC finished with %s uncorrectable errors on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10534: Changed adapter property detected after reboot
| Severity: | MINOR |
| Description: | Changed adapter property detected after reboot. |
| Summary: | Adapter %s: Changed adapter property detected after reboot (Server %s) |
| Resolution: | Check your adapter properties (e.g. via ServerView RAID Manager). |
| go to top | |
10536: Command timeout on disk
| Severity: | MINOR |
| Description: | Command timeout on disk. |
| Summary: | Adapter %s: Command timeout on disk (%s), CDB:%s (Server %s) |
| Note: | Only if problem occurs repeatedly: |
| Resolution: | Proceed with the following steps:
- Check/replace cable between controller and affected disk.
- If problem persists replace affected disk and/or backplane.
|
| go to top | |
10537: Disk reset
| Severity: | MINOR |
| Description: | Disk reset. |
| Summary: | Adapter %s: Disk (%s) reset (type %s) (Server %s) |
| Note: | Only if problem occurs repeatedly: |
| Resolution: | Proceed with the following steps:
- Check/replace cable between controller and affected disk.
- If problem persists replace affected disk.
|
| go to top | |
10538: Bad block table on logical drive is 80 percent full
| Severity: | MINOR |
| Description: | Bad block table on logical drive is 80 percent full. |
| Summary: | Adapter %s: Bad block table on logical drive %s is 80 percent full (Server %s) |
| Resolution: | Check for additional error messages for affected disk. |
| go to top | |
10539: Bad block table on logical drive is full
| Severity: | MAJOR |
| Description: | Bad block table on logical drive is full. |
| Summary: | Adapter %s: Bad block table on logical drive %s is full; unable to log LBA %s (on disk (%s) at LBA %s) (Server %s) |
| Resolution: | Check for additional error messages for affected disk. |
| go to top | |
10540: Uncorrectable medium error logged for logical drive
| Severity: | MAJOR |
| Description: | Uncorrectable medium error logged for logical drive. |
| Summary: | Adapter %s: Uncorrectable medium error logged for logical drive %s at LBA %s (on disk (%s) at LBA %s) (Server %s) |
| Resolution: | Check for additional error messages for affected disk. |
| go to top | |
10542: Bad block table on disk is 100 percent full
| Severity: | MINOR |
| Description: | Bad block table on disk is 100 percent full. |
| Summary: | Adapter %s: Bad block table on disk (%s) is 100 percent full (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10543: Bad block table on logical drive is 100 percent full
| Severity: | MINOR |
| Description: | Bad block table on logical drive is 100 percent full. |
| Summary: | Adapter %s: Bad block table on logical drive %s is 100 percent full (Server %s) |
| Resolution: | Check for additional error messages for affected disk. |
| go to top | |
10551: Copyback failed on disk
| Severity: | MAJOR |
| Description: | Copyback failed on disk. |
| Summary: | Adapter %s: Copyback failed on disk (%s) (Server %s) |
| Resolution: | Check for additional error messages for affected disk. |
| go to top | |
10552: Early power off warning was unsuccessful
| Severity: | MINOR |
| Description: | Early power off warning was unsuccessful. |
| Summary: | Adapter %s: Early power off warning was unsuccessful (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10556: Foreign configuration metadata needs to be upgraded
| Severity: | MINOR |
| Description: | Foreign configuration metadata needs to be upgraded. |
| Summary: | Adapter %s: Foreign configuration metadata needs to be upgraded, may become incompatible (Server %s) |
| Resolution: | For information only. |
| go to top | |
10565: Redundant path broken
| Severity: | MINOR |
| Description: | Redundant path broken. |
| Summary: | Adapter %s: Redundant path broken for disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10567: Redundant enclosure removed
| Severity: | MINOR |
| Description: | Redundant enclosure removed. |
| Summary: | Adapter %s: Redundant enclosure I/O module %s removed for I/O module %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10568: Patrol Read can't be started
| Severity: | MINOR |
| Description: | Patrol Read can't be started. |
| Summary: | Adapter %s: Patrol Read can't be started, all disks are either not online, or are in a logical drive with an active process, or are in an excluded logical drive (Server %s) |
| Resolution: | For information only. |
| go to top | |
10570: Copyback aborted on hot spare
| Severity: | MAJOR |
| Description: | Copyback aborted on hot spare. |
| Summary: | Adapter %s: Copyback aborted on hot spare (%s) from disk (%s) as hot spare needed for rebuild (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10571: Copyback aborted for rebuild
| Severity: | MINOR |
| Description: | Copyback aborted for rebuild. |
| Summary: | Adapter %s: Copyback aborted on disk (%s) from disk (%s) as rebuild required in the array (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10572: Cache discarded for logical drive (missing or offline)
| Severity: | MAJOR |
| Description: | Cache discarded for logical drive (missing or offline). |
| Summary: | Adapter %s: Cache discarded for logical drive (missing or offline) %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10575: Redundancy building failed on disk
| Severity: | MAJOR |
| Description: | Redundancy building failed on disk. |
| Summary: | Adapter %s: Redundancy building failed on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10576: Redundancy building aborted on disk
| Severity: | MINOR |
| Description: | Redundancy building aborted on disk. |
| Summary: | Adapter %s: Redundancy building aborted on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10588: Firmware update timeout on disk
| Severity: | MINOR |
| Description: | Firmware update timeout on disk. |
| Summary: | Adapter %s: Firmware update timeout on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10589: Firmware update failed on disk
| Severity: | MINOR |
| Description: | Firmware update failed on disk. |
| Summary: | Adapter %s: Firmware update failed on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10601: Periodic BBU relearn is pending
| Severity: | MINOR |
| Description: | Periodic BBU relearn is pending. |
| Summary: | Adapter %s: Periodic BBU relearn is pending. Please initiate manual learn cycle as automatic learn is not enabled (Server %s) |
| Resolution: | Initiate manual learn cycle as automatic learn is not enabled. |
| go to top | |
10606: Disk security key, re-key operation failed
| Severity: | MINOR |
| Description: | Disk security key, re-key operation failed. |
| Summary: | Adapter %s: Disk security key, re-key operation failed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10607: Disk security key is invalid
| Severity: | MINOR |
| Description: | Disk security key is invalid. |
| Summary: | Adapter %s: Disk security key is invalid (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10609: Disk security key from escrow is invalid
| Severity: | MINOR |
| Description: | Disk security key from escrow is invalid. |
| Summary: | Adapter %s: Disk security key from escrow is invalid (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10611: Logical drive is partially secured
| Severity: | MINOR |
| Description: | Logical drive is partially secured. |
| Summary: | Adapter %s: Logical drive %s is partially secured (Server %s) |
| Resolution: | For information only. |
| go to top | |
10616: Security subsystem problems detected for disk
| Severity: | MAJOR |
| Description: | Security subsystem problems detected for disk. |
| Summary: | Adapter %s: Security subsystem problems detected for disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10617: Adapter cache preserved for missing or offline logical drive
| Severity: | MAJOR |
| Description: | Adapter cache preserved for missing or offline logical drive. |
| Summary: | Adapter %s: Adapter cache preserved for missing or offline logical drive %s (Server %s) |
| Resolution: | Check error messages for related logical drive and resolve problems. |
| go to top | |
10618: Adapter cache preserved for missing or offline logical drives
| Severity: | MAJOR |
| Description: | Adapter cache preserved for missing or offline logical drives. |
| Summary: | Adapter %s: Adapter cache preserved for missing or offline logical drives (Server %s) |
| Resolution: | Check error messages for related logical drives and resolve problems. |
| go to top | |
10621: MDC started on an inconsistent logical drive
| Severity: | MINOR |
| Description: | MDC started on an inconsistent logical drive. |
| Summary: | Adapter %s: MDC started on an inconsistent logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10622: Disk security key failure, cannot access secured configuration
| Severity: | MINOR |
| Description: | Disk security key failure, cannot access secured configuration. |
| Summary: | Adapter %s: Disk security key failure, cannot access secured configuration (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10623: Disk security pass phrase from user is invalid
| Severity: | MINOR |
| Description: | Disk security pass phrase from user is invalid. |
| Summary: | Adapter %s: Disk security pass phrase from user is invalid (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10625: Abnormal shutdown sequence detected
| Severity: | MINOR |
| Description: | Abnormal shutdown sequence detected. |
| Summary: | Adapter %s: Abnormal shutdown sequence detected (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10626: Internal hardware error
| Severity: | MAJOR |
| Description: | Internal hardware error. |
| Summary: | Adapter %s: Internal hardware error (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10627: Internal hardware error during POST
| Severity: | MAJOR |
| Description: | Internal hardware error during POST. |
| Summary: | Adapter %s: Internal hardware error during POST (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10658: Operation failed
| Severity: | MINOR |
| Description: | Operation failed. |
| Summary: | Adapter %s: Operation failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10660: Array without logical drive left
| Severity: | MINOR |
| Description: | Array without logical drive left. |
| Summary: | Adapter %s: Array %s without logical drive left (Server %s) |
| Resolution: | There is an array which has no logical drive. Create a logical drive to use the array. |
| go to top | |
10661: Incorrect calendar parameter detected
| Severity: | MINOR |
| Description: | Incorrect calendar parameter detected. |
| Summary: | Adapter %s: Incorrect calendar parameter detected (Server %s) |
| Resolution: | Check the scheduler settings. |
| go to top | |
10662: Copyback on logical drive aborted due to bad block table overflow
| Severity: | MAJOR |
| Description: | Copyback on logical drive aborted due to bad block table overflow. |
| Summary: | Adapter %s: Copyback on logical drive %s aborted due to bad block table overflow (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on logical drive.
Proceed with the following steps:
|
| go to top | |
10663: Redundant copy on logical drive aborted due to bad block table overflow
| Severity: | MAJOR |
| Description: | Redundant copy on logical drive aborted due to bad block table overflow. |
| Summary: | Adapter %s: Redundant copy on logical drive %s aborted due to bad block table overflow (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on logical drive.
Proceed with the following steps:
|
| go to top | |
10667: Bad block detected on disk
| Severity: | MINOR |
| Description: | Bad block detected on disk. |
| Summary: | Adapter %s: Bad block detected on disk (%s), %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10672: Error detected on disk
| Severity: | MINOR |
| Description: | Error detected on disk. |
| Summary: | Adapter %s: Error detected on disk (%s), %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10675: Disk location in logical drive changed
| Severity: | MINOR |
| Description: | Disk location in logical drive changed. |
| Summary: | Adapter %s: Disk location in logical drive changed from port %s to port %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10680: Driver error
| Severity: | MINOR |
| Description: | Driver error. |
| Summary: | Adapter %s: Driver error (Server %s) |
| Resolution: | Check the driver version. |
| go to top | |
10682: Copyback aborted on disk
| Severity: | MINOR |
| Description: | Copyback aborted on disk. |
| Summary: | Adapter %s: Copyback aborted on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10684: Internal hardware error
| Severity: | MINOR |
| Description: | Internal hardware error. |
| Summary: | Adapter %s: Internal hardware error (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10685: Internal hardware error
| Severity: | MAJOR |
| Description: | Internal hardware error. |
| Summary: | Adapter %s: Internal hardware error (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10686: Disk bad block table overflow error
| Severity: | MAJOR |
| Description: | Disk bad block table overflow error. |
| Summary: | Adapter %s: Disk (%s) bad block table overflow error (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on the disk.
Proceed with the following steps:
|
| go to top | |
10687: Error with the remote BBU connector cable detected
| Severity: | MINOR |
| Description: | Error with the remote BBU connector cable detected. |
| Summary: | Adapter %s: Error with the remote BBU connector cable detected (Server %s) |
| Resolution: | Replace the BBU data/power cable. |
| go to top | |
10694: Logical drive degraded due to bad block table overflow
| Severity: | MAJOR |
| Description: | Logical drive degraded due to bad block table overflow. |
| Summary: | Adapter %s: Logical drive %s degraded due to bad block table overflow (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on the disk.
Proceed with the following steps:
|
| go to top | |
10696: Abnormal capacity of disk in logical drive detected
| Severity: | MINOR |
| Description: | Abnormal capacity of disk in logical drive detected. |
| Summary: | Adapter %s: Abnormal capacity of disk (%s) in logical drive detected (Server %s) |
| Resolution: | Check the array configuration. |
| go to top | |
10697: Illegal type of disk in logical drive detected
| Severity: | MINOR |
| Description: | Illegal type of disk in logical drive detected. |
| Summary: | Adapter %s: Illegal type of disk (%s) in logical drive detected (Server %s) |
| Resolution: | Check the array configuration. |
| go to top | |
10700: Internal PCI hardware error
| Severity: | MAJOR |
| Description: | Internal PCI hardware error. |
| Summary: | Adapter %s: Internal PCI hardware error (Server %s) |
| Resolution: | Replace affected RAID controller. |
| go to top | |
10701: Bad block table was updated by disk
| Severity: | MINOR |
| Description: | Bad block table was updated by disk. |
| Summary: | Adapter %s: Bad block table was updated by disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10702: Invalid disk on port during start up detected
| Severity: | MINOR |
| Description: | Invalid disk on port during start up detected. |
| Summary: | Adapter %s: Invalid disk on port %s during start up detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10703: Invalid disk on port during hot swap detected
| Severity: | MINOR |
| Description: | Invalid disk on port during hot swap detected. |
| Summary: | Adapter %s: Invalid disk on port %s during hot swap detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10704: SMART error on disk because internal error threshold on adapter is exceeded
| Severity: | MINOR |
| Description: | SMART error on disk because internal error threshold on adapter is exceeded. |
| Summary: | Adapter %s: SMART error on disk (%s) because internal error threshold on adapter is exceeded (Server %s) |
| Note: | Disk reports a prefailure. The affected disk might fail soon. |
| Resolution: | Proceed with the following steps:
- Replace the disk during next maintenance.
|
| go to top | |
10705: Firmware and driver version mismatch
| Severity: | MINOR |
| Description: | Firmware and driver version mismatch. |
| Summary: | Adapter %s: Firmware and driver version mismatch (Server %s) |
| Resolution: | Check the driver and firmware version. |
| go to top | |
10712: Internal software interface error
| Severity: | MINOR |
| Description: | Internal software interface error. |
| Summary: | Adapter %s: Internal software interface error (function: %s) (Server %s) |
| Note: | The driver encountered an error. |
| Resolution: | Proceed with the following steps:
- Check the status of the operating system.
- Reboot your system.
|
| go to top | |
10713: Device open error
| Severity: | MINOR |
| Description: | Device open error. |
| Summary: | Adapter %s: Device open error (device: %s) (Server %s) |
| Note: | The driver encountered an error. |
| Resolution: | Proceed with the following steps:
- Check the status of the operating system.
- Reboot your system.
|
| go to top | |
10714: Ioctl send error
| Severity: | MINOR |
| Description: | Ioctl send error. |
| Summary: | Adapter %s: Ioctl send error (details: %s) (Server %s) |
| Note: | The driver encountered an error. |
| Resolution: | Proceed with the following steps:
- Check the status of the operating system.
- Reboot your system.
|
| go to top | |
10715: Insufficient application memory
| Severity: | MINOR |
| Description: | Insufficient application memory. |
| Summary: | Adapter %s: Insufficient application memory (function: %s) (Server %s) |
| Note: | The driver encountered an error. |
| Resolution: | Proceed with the following steps:
- Check the status of the operating system.
- Reboot your system.
|
| go to top | |
10716: System API error
| Severity: | MINOR |
| Description: | System API error. |
| Summary: | Adapter %s: System API error (code: %s, function/item: %s) (Server %s) |
| Note: | The driver encountered an error. |
| Resolution: | Proceed with the following steps:
- Check the status of the operating system.
- Reboot your system.
|
| go to top | |
10729: BBU requires recalibration
| Severity: | MINOR |
| Description: | BBU requires recalibration. |
| Summary: | Adapter %s: BBU requires reconditioning; please initiate recalibration (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10732: Task for object cannot be started. The scheduler will try to start the task again later
| Severity: | MINOR |
| Description: | Task for object cannot be started. The scheduler will try to start the task again later. |
| Summary: | Task %s for object %s cannot be started (error %s). The scheduler will try to start the task again later (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10734: Task for object cannot be started. The scheduler has disabled the task
| Severity: | MAJOR |
| Description: | Task for object cannot be started. The scheduler has disabled the task. |
| Summary: | Task %s for object %s cannot be started (error %s). The scheduler has disabled the task (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10736: SAS topology error
| Severity: | MAJOR |
| Description: | SAS topology error. |
| Summary: | Adapter %s: SAS topology error: %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10737: BBU requires recalibration automatically initiated
| Severity: | MINOR |
| Description: | BBU requires recalibration automatically initiated. |
| Summary: | Adapter %s: BBU required reconditioning; recalibration initiated (Server %s) |
| Resolution: | For information only. |
| go to top | |
10738: Task for object could not be started at the normal execution time because the service or system was down
| Severity: | MINOR |
| Description: | Task for object could not be started at the normal execution time because the service or system was down. |
| Summary: | Task %s for object %s could not be started at the normal execution time because the service or system was down (Server %s) |
| Resolution: | Check the scheduler settings. |
| go to top | |
10739: Task for object cannot be started. The scheduler will try to start the task again later
| Severity: | MINOR |
| Description: | Task for object cannot be started. The task will be set to the next regular execution time. |
| Summary: | Task %s for object %s cannot be started (error %s). The task will be set to the next regular execution time (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10757: State change from copyback to offline
| Severity: | MINOR |
| Description: | State change from copyback to offline. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10765: State change from JBOD to offline
| Severity: | MINOR |
| Description: | State change from JBOD to offline. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10783: State change by user from copyback to offline
| Severity: | MINOR |
| Description: | State change by user from copyback to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10791: State change by user from JBOD to offline
| Severity: | MINOR |
| Description: | State change by user from JBOD to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
10801: Disk security failed to communicate with external key management system
| Severity: | MINOR |
| Description: | Disk security failed to communicate with external key management system. |
| Summary: | Adapter %s: Disk security failed to communicate with external key management system (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10803: Logical drive secure failed
| Severity: | MINOR |
| Description: | Logical drive secure failed. |
| Summary: | Adapter %s: Logical drive %s secure failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10804: Controller encountered a fatal error and was reset
| Severity: | MAJOR |
| Description: | Controller encountered a fatal error and was reset. |
| Summary: | Adapter %s: Controller encountered a fatal error and was reset (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10805: Configuration command could not be committed to disk
| Severity: | MAJOR |
| Description: | Configuration command could not be committed to disk. |
| Summary: | Adapter %s: Configuration command could not be committed to disk, please retry (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10807: Power state change failed on disk (from active to stopped)
| Severity: | MINOR |
| Description: | Power state change failed on disk (from active to stopped). |
| Summary: | Adapter %s: Power state change failed on disk (%s) (from active to stopped) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10808: Power state change failed on disk (from stopped to active)
| Severity: | MINOR |
| Description: | Power state change failed on disk (from stopped to active). |
| Summary: | Adapter %s: Power state change failed on disk (%s) (from stopped to active) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10809: Logical drive is not ready
| Severity: | MINOR |
| Description: | Logical drive is not ready. |
| Summary: | Adapter %s: Logical drive %s is not ready (Server %s) |
| Resolution: | For information only. |
| go to top | |
10812: Adapter has been replaced during reboot
| Severity: | MINOR |
| Description: | Adapter has been replaced during reboot. |
| Summary: | Adapter %s: Adapter has been replaced during reboot (Server %s) |
| Resolution: | For information only. |
| go to top | |
10813: Enclosure power supply removed
| Severity: | MINOR |
| Description: | Enclosure power supply removed. |
| Summary: | Adapter %s: Enclosure %s power supply %s removed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10814: Enclosure power supply turned off
| Severity: | MINOR |
| Description: | Enclosure power supply turned off. |
| Summary: | Adapter %s: Enclosure %s power supply %s turned off (Server %s) |
| Resolution: | For information only. |
| go to top | |
10817: Enclosure temperature sensor below warning threshold
| Severity: | MINOR |
| Description: | Enclosure temperature sensor below warning threshold. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s below warning threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check environmental temperature.
|
| go to top | |
10818: Enclosure temperature sensor below error threshold
| Severity: | MAJOR |
| Description: | Enclosure temperature sensor below error threshold. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s below error threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check environmental temperature.
|
| go to top | |
10819: Enclosure temperature sensor above warning threshold
| Severity: | MINOR |
| Description: | Enclosure temperature sensor above warning threshold. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s above warning threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
|
| go to top | |
10820: Enclosure temperature sensor above error threshold
| Severity: | MAJOR |
| Description: | Enclosure temperature sensor above error threshold. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s above error threshold (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
|
| go to top | |
10822: Power state change failed on disk (from active to transition)
| Severity: | MINOR |
| Description: | Power state change failed on disk (from active to transition). |
| Summary: | Adapter %s: Power state change failed on disk (%s) (from active to transition) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10824: Power state change failed on disk (from stopped to transition)
| Severity: | MINOR |
| Description: | Power state change failed on disk (from stopped to transition). |
| Summary: | Adapter %s: Power state change failed on disk (%s) (from stopped to transition) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10826: Power state change failed on disk (from transition to active)
| Severity: | MINOR |
| Description: | Power state change failed on disk (from transition to active). |
| Summary: | Adapter %s: Power state change failed on disk (%s) (from transition to active) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10828: Power state change failed on disk (from transition to stopped)
| Severity: | MINOR |
| Description: | Power state change failed on disk (from transition to stopped). |
| Summary: | Adapter %s: Power state change failed on disk (%s) (from transition to stopped) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10829: Reset on-board expander
| Severity: | MINOR |
| Description: | Reset on-board expander. |
| Summary: | Adapter %s: Reset on-board expander (Server %s) |
| Resolution: | For information only. |
| go to top | |
10846: Consistency check rejected on uninitialized logical drive
| Severity: | MINOR |
| Description: | Consistency check rejected on uninitialized logical drive. |
| Summary: | Adapter %s: Consistency check rejected on uninitialized logical drive %s (Server %s) |
| Resolution: | Initiate manual MDC to initialize the logical drive. |
| go to top | |
10852: CacheCade capacity changed
| Severity: | MINOR |
| Description: | CacheCade capacity changed. |
| Summary: | Adapter %s: CacheCade %s capacity changed and is now %s MB (Server %s) |
| Resolution: | For information only. |
| go to top | |
10853: BBU life has degraded and cannot initiate transparent learn cycles
| Severity: | MINOR |
| Description: | BBU life has degraded and cannot initiate transparent learn cycles. |
| Summary: | Adapter %s: BBU life has degraded and cannot initiate transparent learn cycles (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual relearn cycle.
- If problem persists replace BBU.
|
| go to top | |
10857: MegaRAID Advanced Software Options serial number mismatch
| Severity: | MINOR |
| Description: | MegaRAID Advanced Software Options serial number mismatch. |
| Summary: | Adapter %s: MegaRAID Advanced Software Options serial number mismatch. Key Vault serial number is %s (Server %s) |
| Resolution: | Controller serial number does not match with MegaRAID Advanced Software Options key. Apply key to appropriate controller. |
| go to top | |
10858: BBU cannot support data retention
| Severity: | MINOR |
| Description: | BBU cannot support data retention. |
| Summary: | Adapter %s: BBU cannot support data retention for more than %s hours (Server %s) |
| Resolution: | BBU capacity is decreased and buffering of data in controller cache is limited. To reach full data retention time replace BBU. |
| go to top | |
10860: Logical drive cannot transition to maximum power savings
| Severity: | MINOR |
| Description: | Logical drive cannot transition to maximum power savings. |
| Summary: | Adapter %s: Logical drive %s cannot transition to maximum power savings (Server %s) |
| Resolution: | For information only. |
| go to top | |
10864: Disk link failed in SAS wide port
| Severity: | MINOR |
| Description: | Disk link failed in SAS wide port. |
| Summary: | Adapter %s: Disk (%s) link %s failed in SAS wide port (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10867: FBU power pack is sub-optimal
| Severity: | MINOR |
| Description: | FBU power pack is sub-optimal. |
| Summary: | Adapter %s: FBU power pack is sub-optimal (Server %s) |
| Resolution: | Proceed with the following steps:
|
| go to top | |
10868: Foreign configuration auto-import did not import any drives
| Severity: | MINOR |
| Description: | Foreign configuration auto-import did not import any drives. |
| Summary: | Adapter %s: Foreign configuration auto-import did not import any drives (Server %s) |
| Resolution: | Attempt to import a foreign config failed.
Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10869: FBU firmware update required
| Severity: | MINOR |
| Description: | FBU firmware update required. |
| Summary: | Adapter %s: FBU firmware update required (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10870: CacheCade capacity exceeds maximum allowed size
| Severity: | MINOR |
| Description: | CacheCade capacity exceeds maximum allowed size. |
| Summary: | Adapter %s: CacheCade %s capacity exceeds maximum allowed size of %s MB, extra capacity is not used (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10871: Logical drive protection information lost
| Severity: | MINOR |
| Description: | Logical drive protection information lost. |
| Summary: | Adapter %s: Logical drive %s protection information lost (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10873: Diagnostics failed for disk
| Severity: | MAJOR |
| Description: | Diagnostics failed for disk. |
| Summary: | Adapter %s: Diagnostics failed for disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10878: Reminder: Potential non-optimal configuration because disk is commissioned as emergency spare
| Severity: | MINOR |
| Description: | Reminder: Potential non-optimal configuration because disk is commissioned as emergency spare. |
| Summary: | Adapter %s: Reminder: Potential non-optimal configuration because disk (%s) is commissioned as emergency spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10890: Erase failed on disk
| Severity: | MAJOR |
| Description: | Erase failed on disk. |
| Summary: | Adapter %s: Erase failed on disk (%s) (error %s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10895: Erase failed on logical drive
| Severity: | MAJOR |
| Description: | Erase failed on logical drive. |
| Summary: | Adapter %s: Erase failed on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10899: Potential leakage during erase on logical drive
| Severity: | MINOR |
| Description: | Potential leakage during erase on logical drive. |
| Summary: | Adapter %s: Potential leakage during erase on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10900: BBU charging was suspended due to high BBU temperature
| Severity: | MINOR |
| Description: | BBU charging was suspended due to high BBU temperature. |
| Summary: | Adapter %s: BBU charging was suspended due to high BBU temperature (Server %s) |
| Resolution: | Bring system back to normal operating temperature. |
| go to top | |
10902: FBU firmware update failed
| Severity: | MINOR |
| Description: | FBU firmware update failed. |
| Summary: | Adapter %s: FBU firmware update failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10906: CacheCade disassociate failed on logical drive
| Severity: | MAJOR |
| Description: | CacheCade disassociate failed on logical drive. |
| Summary: | Adapter %s: CacheCade disassociate failed on logical drive %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10909: Unexpected sense
| Severity: | MINOR |
| Description: | Unexpected sense. |
| Summary: | Adapter %s: Unexpected sense: Disk (%s), Key/ASC/ASCQ: %s: %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10914: MegaRAID Advanced Software Options were deactivated for
| Severity: | MINOR |
| Description: | MegaRAID Advanced Software Options were deactivated for. |
| Summary: | Adapter %s: MegaRAID Advanced Software Options were deactivated for - %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10918: Patrol Read aborted on disk
| Severity: | MINOR |
| Description: | Patrol Read aborted on disk. |
| Summary: | Adapter %s: Patrol Read aborted on disk (%s) (Server %s) |
| Note: | If there are errors directly before or after this event, perform the proper recovery action for that error. |
| Resolution: | Proceed with the following steps:
|
| go to top | |
10919: Transient error detected while communicating with disk
| Severity: | MINOR |
| Description: | Transient error detected while communicating with disk. |
| Summary: | Adapter %s: Transient error detected while communicating with disk (%s) (Server %s) |
| Note: | Doesn't affect the normal operation of the system, but can lead to degraded performance due to retries. |
| Resolution: | Proceed with the following steps:
- Replace affected disk/backplane/cable at next service.
|
| go to top | |
10924: State change from shielded to offline
| Severity: | MINOR |
| Description: | State change from shielded to offline. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to offline (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10941: State change by user from shielded to offline
| Severity: | MINOR |
| Description: | State change by user from shielded to offline. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to offline (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10959: Write performance reduced
| Severity: | MAJOR |
| Description: | Write performance reduced. |
| Summary: | Adapter %s: Write performance reduced (Server %s) |
| Resolution: | Check additional status property for more information. |
| go to top | |
10960: Write operations disabled
| Severity: | MAJOR |
| Description: | Write operations disabled. |
| Summary: | Adapter %s: Write operations disabled (Server %s) |
| Resolution: | Check additional status property for more information. |
| go to top | |
10961: Temperature close to error threshold
| Severity: | MAJOR |
| Description: | Temperature close to error threshold. |
| Summary: | Adapter %s: Temperature close to error threshold (Server %s) |
| Resolution: | Increase cooling or reduce write load. |
| go to top | |
10967: Temperature above warning threshold
| Severity: | MINOR |
| Description: | Temperature above warning threshold. |
| Summary: | Adapter %s: Temperature above warning threshold (Server %s) |
| Resolution: | Increase cooling or reduce write load. |
| go to top | |
10968: Memory is close to wearing out
| Severity: | MINOR |
| Description: | Memory is close to wearing out. |
| Summary: | Adapter %s: Memory is close to wearing out (Server %s) |
| Resolution: | Formatting to a smaller size will free up reserve. |
| go to top | |
10969: Non-optimal PCI slot bandwidth
| Severity: | MINOR |
| Description: | Non-optimal PCI slot bandwidth. |
| Summary: | Adapter %s: Non-optimal PCI slot bandwidth (Server %s) |
| Resolution: | Reinstall adapter in an optimal PCI slot. |
| go to top | |
10970: Correctable PCI errors detected
| Severity: | MINOR |
| Description: | Correctable PCI errors detected. |
| Summary: | Adapter %s: Correctable PCI errors detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10971: Power loss protection disabled
| Severity: | MINOR |
| Description: | Power loss protection disabled. |
| Summary: | Adapter %s: Power loss protection disabled (Server %s) |
| Resolution: | Activate power loss protection. |
| go to top | |
10972: Write regulation activated due to power constraints of PCI slot
| Severity: | MINOR |
| Description: | Write regulation activated due to power constraints of PCI slot. |
| Summary: | Adapter %s: Write regulation activated due to power constraints of PCI slot (Server %s) |
| Resolution: | If this condition persists, switch to a higher powered PCI slot or attach external power cable. |
| go to top | |
10973: Write regulation activated due to high temperature
| Severity: | MINOR |
| Description: | Write regulation activated due to high temperature. |
| Summary: | Adapter %s: Write regulation activated due to high temperature (Server %s) |
| Resolution: | If this condition persists, increase air flow, lower room temperature or reduce write load. |
| go to top | |
10974: Write regulation activated to ensure adapter lifespan
| Severity: | MINOR |
| Description: | Write regulation activated to ensure adapter lifespan. |
| Summary: | Adapter %s: Write regulation activated to ensure adapter lifespan (Server %s) |
| Resolution: | If this condition persists, reduce write load. |
| go to top | |
10975: Running in minimal status
| Severity: | MINOR |
| Description: | Running in minimal status. |
| Summary: | Adapter %s: Running in minimal status (Server %s) |
| Resolution: | Check additional status property for more information. |
| go to top | |
10976: PCI power budget alarm
| Severity: | MINOR |
| Description: | PCI power budget alarm. |
| Summary: | Adapter %s: PCI power budget alarm (Server %s) |
| Resolution: | Switch to a higher powered PCI slot or attach external power cable. |
| go to top | |
10977: LEB map missing
| Severity: | MINOR |
| Description: | LEB map missing. |
| Summary: | Adapter %s: LEB map missing (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10978: Update in progress
| Severity: | MINOR |
| Description: | Update in progress. |
| Summary: | Adapter %s: Update in progress (Server %s) |
| Resolution: | The adapter will not be usable until formatting is complete. |
| go to top | |
10979: Reserves depleted
| Severity: | MINOR |
| Description: | Reserves depleted. |
| Summary: | Adapter %s: Reserves depleted (Server %s) |
| Resolution: | Formatting to a smaller size will free up reserve. |
| go to top | |
10982: Detach failed
| Severity: | MINOR |
| Description: | Detach failed. |
| Summary: | Adapter %s: Detach failed (Server %s) |
| Resolution: | Proceed with the following steps:
- Force detach.
- If problem persists, call your local Fujitsu Helpdesk.
|
| go to top | |
10989: Protection information error in cache for logical drive
| Severity: | MINOR |
| Description: | Protection information error in cache for logical drive. |
| Summary: | Adapter %s: Protection information error in cache for logical drive %s at LBA %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10990: Flash downloaded image is not supported
| Severity: | MINOR |
| Description: | Flash downloaded image is not supported. |
| Summary: | Adapter %s: Flash downloaded image is not supported (Server %s) |
| Resolution: | For information only. |
| go to top | |
10995: L3 cache error has been detected
| Severity: | MAJOR |
| Description: | L3 cache error has been detected. |
| Summary: | Adapter %s: L3 cache error has been detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10996: L2 cache error has been detected
| Severity: | MAJOR |
| Description: | L2 cache error has been detected. |
| Summary: | Adapter %s: L2 cache error has been detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10997: Adapter booted in headless mode with errors
| Severity: | MINOR |
| Description: | Adapter booted in headless mode with errors. |
| Summary: | Adapter %s: Adapter booted in headless mode with errors (Server %s) |
| Resolution: | For information only. |
| go to top | |
10998: Adapter booted to safe mode due to critical errors
| Severity: | MAJOR |
| Description: | Adapter booted to safe mode due to critical errors. |
| Summary: | Adapter %s: Adapter booted to safe mode due to critical errors (Server %s) |
| Resolution: | For information only. |
| go to top | |
10999: Warning during boot
| Severity: | MINOR |
| Description: | Warning during boot. |
| Summary: | Adapter %s: Warning during boot - %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
11000: Critical error during boot
| Severity: | MAJOR |
| Description: | Critical error during boot. |
| Summary: | Adapter %s: Critical error during boot - %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
11003: Peer adapter has left high availability domain
| Severity: | MAJOR |
| Description: | Peer adapter has left high availability domain. |
| Summary: | Adapter %s: Peer adapter has left high availability domain (ID: %s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
11008: Logical drive has a conflict in high availability domain
| Severity: | MINOR |
| Description: | Logical drive has a conflict in high availability domain. |
| Summary: | Adapter %s: Logical drive %s has a conflict in high availability domain (Server %s) |
| Resolution: | For information only. |
| go to top | |
11011: Logical drive is incompatible in the high availability domain
| Severity: | MINOR |
| Description: | Logical drive is incompatible in the high availability domain. |
| Summary: | Adapter %s: Logical drive %s is incompatible in the high availability domain (Server %s) |
| Resolution: | For information only. |
| go to top | |
11012: Peer adapter is incompatible
| Severity: | MAJOR |
| Description: | Peer adapter is incompatible. |
| Summary: | Adapter %s: Peer adapter is incompatible (Server %s) |
| Resolution: | For information only. |
| go to top | |
11013: Adapters in the high availability domain are incompatible
| Severity: | MAJOR |
| Description: | Adapters in the high availability domain are incompatible. |
| Summary: | Adapter %s: Adapters in the high availability domain are incompatible (Server %s) |
| Resolution: | For information only. |
| go to top | |
11014: Adapter properties are incompatible between local and peer adapters
| Severity: | MAJOR |
| Description: | Adapter properties are incompatible between local and peer adapters. |
| Summary: | Adapter %s: Adapter properties are incompatible between local and peer adapters (Server %s) |
| Resolution: | For information only. |
| go to top | |
11015: Firmware versions do not match in the high availability domain
| Severity: | MINOR |
| Description: | Firmware versions do not match in the high availability domain. |
| Summary: | Adapter %s: Firmware versions do not match in the high availability domain (Server %s) |
| Resolution: | For information only. |
| go to top | |
11016: MegaRAID Advanced Software Options do not match in the high availability domain
| Severity: | MINOR |
| Description: | MegaRAID Advanced Software Options do not match in the high availability domain. |
| Summary: | Adapter %s: MegaRAID Advanced Software Options %s do not match in the high availability domain (Server %s) |
| Resolution: | For information only. |
| go to top | |
11018: High availability cache mirror is offline
| Severity: | MAJOR |
| Description: | High availability cache mirror is offline. |
| Summary: | Adapter %s: High availability cache mirror is offline (Server %s) |
| Resolution: | For information only. |
| go to top | |
11020: FBU power pack is not supported
| Severity: | MINOR |
| Description: | FBU power pack is not supported. |
| Summary: | Adapter %s: FBU power pack is not supported. Please replace the pack (Server %s) |
| Resolution: | For information only. |
| go to top | |
11021: Disk temperature is above warning threshold
| Severity: | MINOR |
| Description: | Disk temperature is above warning threshold. |
| Summary: | Adapter %s: Disk (%s) temperature (%s C) is above warning threshold (Server %s) |
| Resolution: | For information only. |
| go to top | |
11022: Disk temperature is above critical threshold
| Severity: | MAJOR |
| Description: | Disk temperature is above critical threshold. |
| Summary: | Adapter %s: Disk (%s) temperature (%s C) is above critical threshold (Server %s) |
| Resolution: | For information only. |
| go to top | |
11024: Disk IOs are being throttled
| Severity: | MINOR |
| Description: | Disk IOs are being throttled. |
| Summary: | Adapter %s: Disk (%s) IOs are being throttled (Server %s) |
| Resolution: | For information only. |
| go to top | |
11027: Disk life left is below optimal
| Severity: | MINOR |
| Description: | Disk life left is below optimal. |
| Summary: | Adapter %s: Disk (%s) life left (%s percent) is below optimal. Life left thresholds - warning: %s percent, critical: %s percent (Server %s) |
| Resolution: | For information only. |
| go to top | |
11028: Disk life left is critical
| Severity: | MAJOR |
| Description: | Disk life left is critical. |
| Summary: | Adapter %s: Disk (%s) life left (%s percent) is critical. Life left thresholds - warning: %s percent, critical: %s percent (Server %s) |
| Resolution: | For information only. |
| go to top | |
11029: Disk failure device locked-up
| Severity: | MAJOR |
| Description: | Disk failure device locked-up. |
| Summary: | Adapter %s: Disk (%s) failure, device locked-up (Server %s) |
| Resolution: | For information only. |
| go to top | |
11030: Driver needs to be upgraded
| Severity: | MINOR |
| Description: | Driver needs to be upgraded. |
| Summary: | Adapter %s: Driver needs to be upgraded %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
11031: Direct communication with peer adapters was not established
| Severity: | MINOR |
| Description: | Direct communication with peer adapters was not established. |
| Summary: | Adapter %s: Direct communication with peer adapter(s) was not established. Please check proper cable connections (Server %s) |
| Resolution: | For information only. |
| go to top | |
11032: Firmware image does not contain signed component
| Severity: | MINOR |
| Description: | Firmware image does not contain signed component. |
| Summary: | Adapter %s: Firmware image does not contain signed component (Server %s) |
| Resolution: | For information only. |
| go to top | |
11033: Authentication failure of the signed firmware image
| Severity: | MINOR |
| Description: | Authentication failure of the signed firmware image. |
| Summary: | Adapter %s: Authentication failure of the signed firmware image (Server %s) |
| Resolution: | For information only. |
| go to top | |
11038: FBU capacity is too less to support data backup
| Severity: | MAJOR |
| Description: | FBU capacity is too less to support data backup. |
| Summary: | Adapter %s: FBU capacity is too less to support data backup. Write-back logical drives will be converted to Write-through (Server %s) |
| Resolution: | For information only. |
| go to top | |
11039: FBU data backup capacity has decreased consider replacement
| Severity: | MINOR |
| Description: | FBU data backup capacity has decreased consider replacement. |
| Summary: | Adapter %s: FBU data backup capacity has decreased, consider replacement (Server %s) |
| Resolution: | For information only. |
| go to top | |
11040: FBU device failed
| Severity: | MAJOR |
| Description: | FBU device failed. |
| Summary: | Adapter %s: FBU device failed, cannot support data retention (Server %s) |
| Resolution: | For information only. |
| go to top | |
11042: Write-back Nytro cache size mismatch between the servers
| Severity: | MINOR |
| Description: | Write-back Nytro cache size mismatch between the servers. |
| Summary: | Adapter %s: Write-back Nytro cache size mismatch between the servers. The Nytro cache size was adjusted to %s GB (Server %s) |
| Resolution: | For information only. |
| go to top | |
11043: Logical drive is not shared between servers but assigned for caching
| Severity: | MINOR |
| Description: | Logical drive is not shared between servers but assigned for caching. |
| Summary: | Adapter %s: Logical drive %s is not shared between servers but assigned for caching. Write-back Nytro cache content of the logical drive will be mirrored (Server %s) |
| Resolution: | For information only. |
| go to top | |
11048: Temperature threshold exceeded for the adapter
| Severity: | MINOR |
| Description: | Temperature threshold exceeded for the adapter. |
| Summary: | Adapter %s: Temperature threshold exceeded for the adapter. This may indicate inadequate cooling in the system chassis. Adapter has switched to lower performance mode (Server %s) |
| Resolution: | For information only. |
| go to top | |
11049: Adapter defect or no adapter detected on host
| Severity: | MINOR |
| Description: | Adapter defect or no adapter detected on host. |
| Summary: | Adapter defect or no adapter detected on host %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
11050: Connection to host failed
| Severity: | MAJOR |
| Description: | Connection to host failed. |
| Summary: | Connection to host %s failed (Server %s) |
| Resolution: | For information only. |
| go to top | |
11054: FBU components mismatch
| Severity: | MAJOR |
| Description: | FBU components mismatch. |
| Summary: | Adapter %s: FBU components mismatch. Write-back logical drives will be converted to write-through (Server %s) |
| Resolution: | For information only. |
| go to top | |
11058: Cannot enter mode because logical drive would not be supported
| Severity: | MAJOR |
| Description: | Cannot enter mode because logical drive would not be supported. |
| Summary: | Adapter %s: Cannot enter %s mode because %s logical drive %s would not be supported (Server %s) |
| Resolution: | For information only. |
| go to top | |
11059: Cannot enter mode because disk would not be supported
| Severity: | MAJOR |
| Description: | Cannot enter mode because disk would not be supported. |
| Summary: | Adapter %s: Cannot enter %s mode because %s disk (%s) would not be supported (Server %s) |
| Resolution: | For information only. |
| go to top | |
1: Undefined event
| Severity: | INFORMATIONAL |
| Description: | Undefined event. |
| Summary: | Undefined event (Server %s) |
| Resolution: | If there are errors directly before or after this event, perform the proper recovery action for that error. |
| go to top | |
2: Connection to ServerView RAID Manager established
| Severity: | INFORMATIONAL |
| Description: | Connection to ServerView RAID Manager established. |
| Summary: | Connection to ServerView RAID Manager established (Server %s) |
| Resolution: | If there are errors directly before or after this event, perform the proper recovery action for that error. |
| go to top | |
3: Disconnected from ServerView RAID Manager
| Severity: | INFORMATIONAL |
| Description: | Disconnected from ServerView RAID Manager. |
| Summary: | Disconnected from ServerView RAID Manager (Server %s) |
| Resolution: | If there are errors directly before or after this event, perform the proper recovery action for that error. |
| go to top | |
5: Test event
| Severity: | INFORMATIONAL |
| Description: | Test event. |
| Summary: | Test event (Server %s) |
| Resolution: | If problem persists after reboot, call your local Fujitsu Helpdesk. |
| go to top | |
10000: Unknown event
| Severity: | INFORMATIONAL |
| Description: | Unknown event. |
| Summary: | Unknown event (Server %s) |
| Resolution: | If there are errors directly before or after this event, perform the proper recovery action for that error. |
| go to top | |
10001: Internal event
| Severity: | INFORMATIONAL |
| Description: | Internal event. |
| Summary: | Internal event (Server %s) |
| Resolution: | For information only. |
| go to top | |
10010: BBU reconditioning started
| Severity: | INFORMATIONAL |
| Description: | BBU reconditioning started. |
| Summary: | Adapter %s: BBU reconditioning started (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10011: BBU status becomes normal
| Severity: | INFORMATIONAL |
| Description: | BBU status becomes normal. |
| Summary: | Adapter %s: BBU status becomes normal (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10012: BBU good
| Severity: | INFORMATIONAL |
| Description: | BBU good. |
| Summary: | Adapter %s: BBU good (Server %s) |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10017: SCSI sense data available
| Severity: | INFORMATIONAL |
| Description: | SCSI sense data available. |
| Summary: | Adapter %s: SCSI sense data on disk (%s) available: %s (Server %s) |
| Note: | By default BBU recalibration is automatically initiated every 30 days. |
| Resolution: | Proceed with the following steps:
- If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID Manager).
|
| go to top | |
10018: Asynchronous command finished
| Severity: | INFORMATIONAL |
| Description: | Asynchronous command finished. |
| Summary: | Adapter %s: Asynchronous command finished (Server %s) |
| Note: | By default BBU recalibration is automatically initiated every 30 days. |
| Resolution: | Proceed with the following steps:
- If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID Manager).
|
| go to top | |
10019: Adapter suspended
| Severity: | INFORMATIONAL |
| Description: | Adapter suspended. |
| Summary: | Adapter %s suspended (Server %s) |
| Note: | By default BBU recalibration is automatically initiated every 30 days. |
| Resolution: | Proceed with the following steps:
- If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID Manager).
|
| go to top | |
10020: Adapter resumed
| Severity: | INFORMATIONAL |
| Description: | Adapter resumed. |
| Summary: | Adapter %s resumed (Server %s) |
| Note: | By default BBU recalibration is automatically initiated every 30 days. |
| Resolution: | Proceed with the following steps:
- If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID Manager).
|
| go to top | |
10021: Disk marked online
| Severity: | INFORMATIONAL |
| Description: | Disk marked online. |
| Summary: | Adapter %s: Disk (%s) marked online (Server %s) |
| Note: | By default BBU recalibration is automatically initiated every 30 days. |
| Resolution: | Proceed with the following steps:
- If scheduled BBU recalibration is disabled initiate manual recalibration process (e.g. via ServerView RAID Manager).
|
| go to top | |
10024: Global hot spare created on disk
| Severity: | INFORMATIONAL |
| Description: | Global hot spare created on disk. |
| Summary: | Adapter %s: Global hot spare created on disk (%s) (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10026: Dedicated hot spare created on disk
| Severity: | INFORMATIONAL |
| Description: | Dedicated hot spare created on disk. |
| Summary: | Adapter %s: Dedicated hot spare created on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10028: Disk marked available
| Severity: | INFORMATIONAL |
| Description: | Disk marked available. |
| Summary: | Adapter %s: Disk (%s) marked available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10029: Rebuild on disk started
| Severity: | INFORMATIONAL |
| Description: | Rebuild on disk started. |
| Summary: | Adapter %s: Rebuild on disk (%s) started (Server %s) |
| Resolution: | For information only. |
| go to top | |
10032: New disk detected
| Severity: | INFORMATIONAL |
| Description: | New disk detected. |
| Summary: | Adapter %s: New disk (%s) detected (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10034: Bad sector log entry on disk cleared
| Severity: | INFORMATIONAL |
| Description: | Bad sector log entry on disk cleared. |
| Summary: | Adapter %s: Bad sector log entry on disk (%s) cleared (Server %s) |
| Note: | Only informational if affected disk has been removed otherwise: |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10035: Bad sector log on disk updated
| Severity: | INFORMATIONAL |
| Description: | Bad sector log on disk updated. |
| Summary: | Adapter %s: Bad sector log on disk (%s) updated (Server %s) |
| Note: | Only informational if affected disk has been removed otherwise: |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10039: Channel was reset
| Severity: | INFORMATIONAL |
| Description: | Channel was reset. |
| Summary: | Adapter %s: Channel %s was reset (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10042: Write mode changed
| Severity: | INFORMATIONAL |
| Description: | Write mode changed. |
| Summary: | Adapter %s: Write modes changed (Server %s) |
| Resolution: | If the problem occurs repeatedly replace affected disk. |
| go to top | |
10048: Enclosure powered up
| Severity: | INFORMATIONAL |
| Description: | Enclosure powered up. |
| Summary: | Adapter %s: Enclosure %s powered up (Server %s) |
| Resolution: | If this error message is not a result of a planned power off of the external storage subsystem:
Proceed with the following steps:
- Check the power cable(s).
- Check the mains voltage.
- Replace affected power supply(s).
|
| go to top | |
10055: Rebuild started on logical drive
| Severity: | INFORMATIONAL |
| Description: | Rebuild started on logical drive. |
| Summary: | Adapter %s: Rebuild started on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Check whether all cables are correctly connected to the disk backplane connectors.
- Replace affected disk.
|
| go to top | |
10056: Rebuild finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | Rebuild finished on logical drive. |
| Summary: | Adapter %s: Rebuild finished on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Check whether all cables are correctly connected to the disk backplane connectors.
- Replace affected disk.
|
| go to top | |
10059: Rebuild suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Rebuild suspended on logical drive. |
| Summary: | Adapter %s: Rebuild suspended on logical drive %s (Server %s) |
| Note: | Rebuild was probably aborted by user. Attention: The affected RAID array is still degraded. |
| Resolution: | Proceed with the following steps:
- The rebuild should be started again as soon as possible.
|
| go to top | |
10060: Consistency check started on logical drive
| Severity: | INFORMATIONAL |
| Description: | Consistency check started on logical drive. |
| Summary: | Adapter %s: Consistency check started on logical drive %s (Server %s) |
| Note: | Rebuild was probably aborted by user. Attention: The affected RAID array is still degraded. |
| Resolution: | Proceed with the following steps:
- The rebuild should be started again as soon as possible.
|
| go to top | |
10061: Consistency check finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | Consistency check finished on logical drive. |
| Summary: | Adapter %s: Consistency check finished on logical drive %s (Server %s) |
| Note: | Rebuild was probably aborted by user. Attention: The affected RAID array is still degraded. |
| Resolution: | Proceed with the following steps:
- The rebuild should be started again as soon as possible.
|
| go to top | |
10064: Consistency check suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Consistency check suspended on logical drive. |
| Summary: | Adapter %s: Consistency check suspended on logical drive %s (Server %s) |
| Note: | Consistency check was probably aborted by user. |
| Resolution: | Proceed with the following steps:
- The consistency check should be started again as soon as possible.
|
| go to top | |
10065: Consistency check started on uninitialized logical drive
| Severity: | INFORMATIONAL |
| Description: | Consistency check started on uninitialized logical drive. |
| Summary: | Adapter %s: Consistency check started on uninitialized logical drive %s (Server %s) |
| Note: | Consistency check was probably aborted by user. |
| Resolution: | Proceed with the following steps:
- The consistency check should be started again as soon as possible.
|
| go to top | |
10068: Migration started on logical drive
| Severity: | INFORMATIONAL |
| Description: | Migration started on logical drive. |
| Summary: | Adapter %s: Migration started on logical drive %s (Server %s) |
| Resolution: | Check if logical drive is initialized. If initialized check the following:
Proceed with the following steps:
- Backup your data.
- Start a consistency check with fix.
- Compare backup data with data on logical drive.
- If different (data lost), restore last good data.
|
| go to top | |
10069: Migration finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | Migration finished on logical drive. |
| Summary: | Adapter %s: Migration finished on logical drive %s (Server %s) |
| Resolution: | Check if logical drive is initialized. If initialized check the following:
Proceed with the following steps:
- Backup your data.
- Start a consistency check with fix.
- Compare backup data with data on logical drive.
- If different (data lost), restore last good data.
|
| go to top | |
10072: Patrol Read started
| Severity: | INFORMATIONAL |
| Description: | Patrol Read started. |
| Summary: | Adapter %s: Patrol Read started (Server %s) |
| Resolution: | Note: Migration was probably aborted by user. For information only. |
| go to top | |
10073: Patrol Read finished
| Severity: | INFORMATIONAL |
| Description: | Patrol Read finished. |
| Summary: | Adapter %s: Patrol Read finished (Server %s) |
| Resolution: | Note: Migration was probably aborted by user. For information only. |
| go to top | |
10075: Patrol Read stopped
| Severity: | INFORMATIONAL |
| Description: | Patrol Read stopped. |
| Summary: | Adapter %s: Patrol Read stopped (Server %s) |
| Resolution: | Note: Patrol read was probably aborted by user. For information only. |
| go to top | |
10076: Patrol Read suspended
| Severity: | INFORMATIONAL |
| Description: | Patrol Read suspended. |
| Summary: | Adapter %s: Patrol Read suspended (Server %s) |
| Resolution: | Note: Patrol read was probably aborted by user. For information only. |
| go to top | |
10077: Patrol Read resumed
| Severity: | INFORMATIONAL |
| Description: | Patrol Read resumed. |
| Summary: | Adapter %s: Patrol Read resumed (Server %s) |
| Resolution: | Note: Patrol read was probably aborted by user. For information only. |
| go to top | |
10080: Logical drive created
| Severity: | INFORMATIONAL |
| Description: | Logical drive created. |
| Summary: | Adapter %s: Logical drive %s created (Server %s) |
| Resolution: | Note: Sometimes it is possible to recover without data loss. Further investigation is needed. |
| go to top | |
10082: Logical drive operational
| Severity: | INFORMATIONAL |
| Description: | Logical drive operational. |
| Summary: | Adapter %s: Logical drive %s operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10085: Initialization started on logical drive
| Severity: | INFORMATIONAL |
| Description: | Initialization started on logical drive. |
| Summary: | Adapter %s: Initialization started on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Try to rewrite data.
- If problem persists replace affected disk.
|
| go to top | |
10086: Initialization finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | Initialization finished on logical drive. |
| Summary: | Adapter %s: Initialization finished on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Try to rewrite data.
- If problem persists replace affected disk.
|
| go to top | |
10087: BGI started on logical drive
| Severity: | INFORMATIONAL |
| Description: | BGI started on logical drive. |
| Summary: | Adapter %s: BGI started on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Try to rewrite data.
- If problem persists replace affected disk.
|
| go to top | |
10088: BGI finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | BGI finished on logical drive. |
| Summary: | Adapter %s: BGI finished on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Try to rewrite data.
- If problem persists replace affected disk.
|
| go to top | |
10091: Drive letter changed for logical drive
| Severity: | INFORMATIONAL |
| Description: | Drive letter changed for logical drive. |
| Summary: | Adapter %s: Drive letter changed for logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10092: Hot spare operation on logical drive started
| Severity: | INFORMATIONAL |
| Description: | Hot spare operation on logical drive started. |
| Summary: | Adapter %s: Hot spare operation on logical drive %s started (Server %s) |
| Resolution: | For information only. |
| go to top | |
10095: Alarm enabled
| Severity: | INFORMATIONAL |
| Description: | Alarm enabled. |
| Summary: | Adapter %s: Alarm enabled (Server %s) |
| Resolution: | Proceed with the following steps:
- Temporary offline case.
- Try to rebuild remaining defect drive.
|
| go to top | |
10097: Automatic inconsistency handling enabled
| Severity: | INFORMATIONAL |
| Description: | Automatic inconsistency handling enabled. |
| Summary: | Adapter %s: Automatic inconsistency handling enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10098: Automatic inconsistency handling disabled
| Severity: | INFORMATIONAL |
| Description: | Automatic inconsistency handling disabled. |
| Summary: | Adapter %s: Automatic inconsistency handling disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10099: Automatic inconsistency handling Interval changed
| Severity: | INFORMATIONAL |
| Description: | Automatic inconsistency handling Interval changed. |
| Summary: | Adapter %s: Inconsistency handling interval changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10100: Rebuild rate changed
| Severity: | INFORMATIONAL |
| Description: | Rebuild rate changed. |
| Summary: | Adapter %s: Rebuild rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10101: Patrol Read disabled
| Severity: | INFORMATIONAL |
| Description: | Patrol Read disabled. |
| Summary: | Adapter %s: Patrol Read disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10102: Patrol Read set to automatic
| Severity: | INFORMATIONAL |
| Description: | Patrol Read set to automatic. |
| Summary: | Adapter %s: Patrol Read set to automatic (Server %s) |
| Resolution: | For information only. |
| go to top | |
10103: Patrol Read set to manual
| Severity: | INFORMATIONAL |
| Description: | Patrol Read set to manual. |
| Summary: | Adapter %s: Patrol Read set to manual (Server %s) |
| Resolution: | For information only. |
| go to top | |
10104: Patrol Read delay changed
| Severity: | INFORMATIONAL |
| Description: | Patrol Read delay changed. |
| Summary: | Adapter %s: Patrol Read delay changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10105: Initialization set to normal
| Severity: | INFORMATIONAL |
| Description: | Initialization set to normal. |
| Summary: | Adapter %s: Initialization set to normal (Server %s) |
| Resolution: | For information only. |
| go to top | |
10106: Initialization set to fast
| Severity: | INFORMATIONAL |
| Description: | Initialization set to fast. |
| Summary: | Adapter %s: Initialization set to fast (Server %s) |
| Resolution: | For information only. |
| go to top | |
10107: Initiator ID changed
| Severity: | INFORMATIONAL |
| Description: | Initiator ID changed. |
| Summary: | Adapter %s: Initiator ID changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10108: Automatic rebuild enabled
| Severity: | INFORMATIONAL |
| Description: | Automatic rebuild enabled. |
| Summary: | Adapter %s: Automatic rebuild enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10109: Automatic rebuild disabled
| Severity: | INFORMATIONAL |
| Description: | Automatic rebuild disabled. |
| Summary: | Adapter %s: Automatic rebuild disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10110: New device set to automatic
| Severity: | INFORMATIONAL |
| Description: | New device set to automatic. |
| Summary: | Adapter %s: New device set to automatic (Server %s) |
| Resolution: | For information only. |
| go to top | |
10111: New device set to CTRL-M
| Severity: | INFORMATIONAL |
| Description: | New device set to CTRL-M. |
| Summary: | Adapter %s: New device set to CtrlM (Server %s) |
| Resolution: | For information only. |
| go to top | |
10112: MDC rate changed
| Severity: | INFORMATIONAL |
| Description: | MDC rate changed. |
| Summary: | Adapter %s: MDC rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10113: MDC rate changed
| Severity: | INFORMATIONAL |
| Description: | MDC rate changed. |
| Summary: | Adapter %s: MDC rate changed to %s percent (Server %s) |
| Resolution: | For information only. |
| go to top | |
10114: BIOS enabled
| Severity: | INFORMATIONAL |
| Description: | BIOS enabled. |
| Summary: | Adapter %s: BIOS enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10115: BIOS disabled
| Severity: | INFORMATIONAL |
| Description: | BIOS disabled. |
| Summary: | Adapter %s: BIOS disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10116: BIOS stop on error enabled
| Severity: | INFORMATIONAL |
| Description: | BIOS stop on error enabled. |
| Summary: | Adapter %s: BIOS stop on error enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10117: BIOS stop on error disabled
| Severity: | INFORMATIONAL |
| Description: | BIOS stop on error disabled. |
| Summary: | Adapter %s: BIOS stop on error disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10118: Write cache on all disks enabled
| Severity: | INFORMATIONAL |
| Description: | Write cache on all disks enabled. |
| Summary: | Adapter %s: Write cache on all disks enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10119: Write cache on all disks disabled
| Severity: | INFORMATIONAL |
| Description: | Write cache on all disks disabled. |
| Summary: | Adapter %s: Write cache on all disks disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10120: Read-ahead on all disks enabled
| Severity: | INFORMATIONAL |
| Description: | Read-ahead on all disks enabled. |
| Summary: | Adapter %s: Read-ahead on all disks enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10121: Read-ahead on all disks disabled
| Severity: | INFORMATIONAL |
| Description: | Read-ahead on all disks disabled. |
| Summary: | Adapter %s: Read-ahead on all disks disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10122: Automatic resumption enabled
| Severity: | INFORMATIONAL |
| Description: | Automatic resumption enabled. |
| Summary: | Adapter %s: Automatic resumption enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10123: Automatic resumption disabled
| Severity: | INFORMATIONAL |
| Description: | Automatic resumption disabled. |
| Summary: | Adapter %s: Automatic resumption disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10124: Spinup drive count changed (after next reboot)
| Severity: | INFORMATIONAL |
| Description: | Spinup drive count changed (after next reboot). |
| Summary: | Adapter %s: Spinup drive count changed (after next reboot) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10125: Spinup delay changed (after next reboot)
| Severity: | INFORMATIONAL |
| Description: | Spinup delay changed (after next reboot). |
| Summary: | Adapter %s: Spinup delay changed (after next reboot) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10126: Consistency check rate changed
| Severity: | INFORMATIONAL |
| Description: | Consistency check rate changed. |
| Summary: | Adapter %s: Consistency check rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10127: Temporary offline enabled
| Severity: | INFORMATIONAL |
| Description: | Temporary offline enabled. |
| Summary: | Adapter %s: Temporary offline enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10128: Temporary offline disabled
| Severity: | INFORMATIONAL |
| Description: | Temporary offline disabled. |
| Summary: | Adapter %s: Temporary offline disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10129: SMART enabled
| Severity: | INFORMATIONAL |
| Description: | SMART enabled. |
| Summary: | Adapter %s: SMART enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10130: SMART disabled
| Severity: | INFORMATIONAL |
| Description: | SMART disabled. |
| Summary: | Adapter %s: SMART disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10131: SMART poll interval changed
| Severity: | INFORMATIONAL |
| Description: | SMART poll interval changed. |
| Summary: | Adapter %s: SMART poll interval changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10132: Configuration rescanned
| Severity: | INFORMATIONAL |
| Description: | Configuration rescanned. |
| Summary: | Adapter %s: Configuration rescanned (Server %s) |
| Resolution: | For information only. |
| go to top | |
10133: Configuration cleared
| Severity: | INFORMATIONAL |
| Description: | Configuration cleared. |
| Summary: | Adapter %s: Configuration cleared (Server %s) |
| Resolution: | For information only. |
| go to top | |
10134: Activity changed
| Severity: | INFORMATIONAL |
| Description: | Activity changed. |
| Summary: | Adapter %s: Activity changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10135: Channel termination set to wide
| Severity: | INFORMATIONAL |
| Description: | Channel termination set to wide. |
| Summary: | Adapter %s: Channel %s termination set to wide (Server %s) |
| Resolution: | For information only. |
| go to top | |
10136: Channel termination set to narrow
| Severity: | INFORMATIONAL |
| Description: | Channel termination set to narrow. |
| Summary: | Adapter %s: Channel %s termination set to narrow (Server %s) |
| Resolution: | For information only. |
| go to top | |
10137: Channel termination disabled
| Severity: | INFORMATIONAL |
| Description: | Channel termination disabled. |
| Summary: | Adapter %s: Channel %s termination disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10138: Channel activated
| Severity: | INFORMATIONAL |
| Description: | Channel activated. |
| Summary: | Adapter %s: Channel %s activated (Server %s) |
| Resolution: | For information only. |
| go to top | |
10140: Channel set to dedicated
| Severity: | INFORMATIONAL |
| Description: | Channel set to dedicated. |
| Summary: | Adapter %s: Channel %s set to dedicated (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10141: Channel set to shared
| Severity: | INFORMATIONAL |
| Description: | Channel set to shared. |
| Summary: | Adapter %s: Channel %s set to shared (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10142: Logical drive: Read-ahead enabled
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Read-ahead enabled. |
| Summary: | Adapter %s: Logical drive %s: Read-ahead enabled (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10143: Logical drive: Read-ahead disabled
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Read-ahead disabled. |
| Summary: | Adapter %s: Logical drive %s: Read-ahead disabled (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10144: Logical drive: Adaptive read-ahead enabled
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Adaptive read-ahead enabled. |
| Summary: | Adapter %s: Logical drive %s: Adaptive read-ahead enabled (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10145: Logical drive: Write mode set to Write-through
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Write mode set to Write-through. |
| Summary: | Adapter %s: Logical drive %s: Write mode set to Write-through (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10146: Logical drive: Write mode set to Write-back
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Write mode set to Write-back. |
| Summary: | Adapter %s: Logical drive %s: Write mode set to Write-back (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10147: Logical drive: I/O mode set to direct
| Severity: | INFORMATIONAL |
| Description: | Logical drive: I/O mode set to direct. |
| Summary: | Adapter %s: Logical drive %s: I/O mode set to direct (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10148: Logical drive: I/O mode set to cached
| Severity: | INFORMATIONAL |
| Description: | Logical drive: I/O mode set to cached. |
| Summary: | Adapter %s: Logical drive %s: I/O mode set to cached (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10149: Max. transfer speed of disk changed (after next Reboot)
| Severity: | INFORMATIONAL |
| Description: | Max. transfer speed of disk changed (after next Reboot). |
| Summary: | Adapter %s: Max. transfer speed of disk (%s) changed (after next reboot) (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10150: Bus width of disk changed (after next Reboot)
| Severity: | INFORMATIONAL |
| Description: | Bus width of disk changed (after next Reboot). |
| Summary: | Adapter %s: Bus width of disk (%s) changed (after next reboot) (Server %s) |
| Resolution: | Proceed with the following steps:
- Connection issue.
- Check all of your cabling.
|
| go to top | |
10153: BBU charging
| Severity: | INFORMATIONAL |
| Description: | BBU charging. |
| Summary: | Adapter %s: BBU charging (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10155: BBU normal
| Severity: | INFORMATIONAL |
| Description: | BBU normal. |
| Summary: | Adapter %s: BBU normal (Server %s) |
| Note: | Only informational during recalibration process. |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10156: BBU discharging
| Severity: | INFORMATIONAL |
| Description: | BBU discharging. |
| Summary: | Adapter %s: BBU discharging (Server %s) |
| Note: | Only informational during recalibration process. |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10158: Driver write cache enabled
| Severity: | INFORMATIONAL |
| Description: | Driver write cache enabled. |
| Summary: | Adapter %s: Driver write cache enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10159: Driver write cache disabled
| Severity: | INFORMATIONAL |
| Description: | Driver write cache disabled. |
| Summary: | Adapter %s: Driver write cache disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10160: Drive sizing (GB Boundary) enabled
| Severity: | INFORMATIONAL |
| Description: | Drive sizing (GB Boundary) enabled. |
| Summary: | Adapter %s: Drive sizing (GB boundary) enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10161: Drive sizing (GB Boundary) disabled
| Severity: | INFORMATIONAL |
| Description: | Drive sizing (GB Boundary) disabled. |
| Summary: | Adapter %s: Drive sizing (GB boundary) disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10162: Hot spare support and automatic rebuild enabled
| Severity: | INFORMATIONAL |
| Description: | Hot spare support and automatic rebuild enabled. |
| Summary: | Adapter %s: Hot spare support and automatic rebuild enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10163: Hot spare support and automatic rebuild disabled
| Severity: | INFORMATIONAL |
| Description: | Hot spare support and automatic rebuild disabled. |
| Summary: | Adapter %s: Hot spare support and automatic rebuild disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10164: Task rate changed
| Severity: | INFORMATIONAL |
| Description: | Task rate changed. |
| Summary: | Adapter %s: Task rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10165: Inconsistency handling set to consistency check
| Severity: | INFORMATIONAL |
| Description: | Inconsistency handling set to consistency check. |
| Summary: | Adapter %s: Inconsistency handling set to consistency check (Server %s) |
| Resolution: | For information only. |
| go to top | |
10166: Inconsistency handling set to consistency check (abort on first inconsistency)
| Severity: | INFORMATIONAL |
| Description: | Inconsistency handling set to consistency check (abort on first inconsistency). |
| Summary: | Adapter %s: Inconsistency handling set to consistency check (abort on first inconsistency) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10167: Inconsistency handling set to MDC
| Severity: | INFORMATIONAL |
| Description: | Inconsistency handling set to MDC. |
| Summary: | Adapter %s: Inconsistency handling set to MDC (Server %s) |
| Resolution: | For information only. |
| go to top | |
10168: Logical drive: Name changed
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Name changed. |
| Summary: | Adapter %s: Logical drive %s: Name changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10169: Logical drive: Cache write mode changed
| Severity: | INFORMATIONAL |
| Description: | Logical drive: Cache write mode changed. |
| Summary: | Adapter %s: Logical drive %s: Cache write mode changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10171: Module logged in
| Severity: | INFORMATIONAL |
| Description: | Module logged in. |
| Summary: | User %s (%s) logged in (Server %s) |
| Resolution: | For information only. |
| go to top | |
10172: Module logged out
| Severity: | INFORMATIONAL |
| Description: | Module logged out. |
| Summary: | User %s (%s) logged out (Server %s) |
| Resolution: | For information only. |
| go to top | |
10173: Hot spare enabled
| Severity: | INFORMATIONAL |
| Description: | Hot spare enabled. |
| Summary: | Adapter %s: Hot spare enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10174: Hot spare disabled
| Severity: | INFORMATIONAL |
| Description: | Hot spare disabled. |
| Summary: | Adapter %s: Hot spare disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10175: Hotswap enabled
| Severity: | INFORMATIONAL |
| Description: | Hotswap enabled. |
| Summary: | Adapter %s: Hot swap enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10176: Hotswap disabled
| Severity: | INFORMATIONAL |
| Description: | Hotswap disabled. |
| Summary: | Adapter %s: Hot swap disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10177: Write mode set to Write-back
| Severity: | INFORMATIONAL |
| Description: | Write mode set to Write-back. |
| Summary: | Adapter %s: Write mode set to Write-back (Server %s) |
| Resolution: | For information only. |
| go to top | |
10178: Write mode set to Write-through
| Severity: | INFORMATIONAL |
| Description: | Write mode set to Write-through. |
| Summary: | Adapter %s: Write mode set to Write-through (Server %s) |
| Resolution: | For information only. |
| go to top | |
10179: Write mode set to adaptive
| Severity: | INFORMATIONAL |
| Description: | Write mode set to adaptive. |
| Summary: | Adapter %s: Write mode set to Adaptive (Server %s) |
| Resolution: | For information only. |
| go to top | |
10180: BBU charging started
| Severity: | INFORMATIONAL |
| Description: | BBU charging started. |
| Summary: | Adapter %s: BBU charging started (Server %s) |
| Resolution: | For information only. |
| go to top | |
10181: Automatic initialization of RAID-5 enabled
| Severity: | INFORMATIONAL |
| Description: | Automatic initialization of RAID-5 enabled. |
| Summary: | Adapter %s: Automatic initialization of RAID-5 enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10182: Automatic initialization of RAID-5 disabled
| Severity: | INFORMATIONAL |
| Description: | Automatic initialization of RAID-5 disabled. |
| Summary: | Adapter %s: Automatic initialization of RAID-5 disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10183: Copyback enabled
| Severity: | INFORMATIONAL |
| Description: | Copyback enabled. |
| Summary: | Adapter %s: Copyback enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10184: Copyback disabled
| Severity: | INFORMATIONAL |
| Description: | Copyback disabled. |
| Summary: | Adapter %s: Copyback disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10185: Initialization set to clear
| Severity: | INFORMATIONAL |
| Description: | Initialization set to clear. |
| Summary: | Adapter %s: Initialization set to clear (Server %s) |
| Resolution: | For information only. |
| go to top | |
10186: Verify started
| Severity: | INFORMATIONAL |
| Description: | Verify started. |
| Summary: | Adapter %s: Verification started on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10187: Verify finished
| Severity: | INFORMATIONAL |
| Description: | Verify finished. |
| Summary: | Adapter %s: Verification finished on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10188: Cache read mode changed
| Severity: | INFORMATIONAL |
| Description: | Cache read mode changed. |
| Summary: | Adapter %s: Logical drive %s: Cache read mode changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10189: Cache mode changed
| Severity: | INFORMATIONAL |
| Description: | Cache mode changed. |
| Summary: | Adapter %s: Logical drive %s: Cache mode changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10190: Access mode changed
| Severity: | INFORMATIONAL |
| Description: | Access mode changed. |
| Summary: | Adapter %s: Logical drive %s: Access mode changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10191: BGI mode changed
| Severity: | INFORMATIONAL |
| Description: | BGI mode changed. |
| Summary: | Adapter %s: Logical drive %s: BGI mode changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10192: Disk cache mode changed
| Severity: | INFORMATIONAL |
| Description: | Disk cache mode changed. |
| Summary: | Adapter %s: Logical drive %s: Disk cache mode changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10193: Firmware initialization started
| Severity: | INFORMATIONAL |
| Description: | Firmware initialization started. |
| Summary: | Adapter %s: Firmware initialization started (Server %s) |
| Resolution: | For information only. |
| go to top | |
10194: Firmware version
| Severity: | INFORMATIONAL |
| Description: | Firmware version. |
| Summary: | Adapter %s: Firmware version %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10196: Cache data recovered from TBBU successfully
| Severity: | INFORMATIONAL |
| Description: | Cache data recovered from TBBU successfully. |
| Summary: | Adapter %s: Cache data recovered from TBBU successfully (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10198: Ownership changed
| Severity: | INFORMATIONAL |
| Description: | Ownership changed. |
| Summary: | Adapter %s: %s ownership changed from %s to %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10199: Background initialization rate changed
| Severity: | INFORMATIONAL |
| Description: | Background initialization rate changed. |
| Summary: | Adapter %s: BGI rate changed to %s percent (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10202: Cache data recovered successfully
| Severity: | INFORMATIONAL |
| Description: | Cache data recovered successfully. |
| Summary: | Adapter %s: Cache data recovered successfully (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10205: Factory defaults restored
| Severity: | INFORMATIONAL |
| Description: | Factory defaults restored. |
| Summary: | Adapter %s: Factory defaults restored (Server %s) |
| Resolution: | Proceed with the following steps:
- Disconnect AC and wait 30 seconds before reconnect.
|
| go to top | |
10210: Flashing image
| Severity: | INFORMATIONAL |
| Description: | Flashing image. |
| Summary: | Adapter %s: Flashing image: %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10211: Flash complete
| Severity: | INFORMATIONAL |
| Description: | Flash complete. |
| Summary: | Adapter %s: Flash of new firmware image(s) complete (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10217: Flush rate changed
| Severity: | INFORMATIONAL |
| Description: | Flush rate changed. |
| Summary: | Adapter %s: Flush rate changed to %s seconds (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10218: Hibernate command received
| Severity: | INFORMATIONAL |
| Description: | Hibernate command received. |
| Summary: | Adapter %s: Hibernate command received from host (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10219: Event log cleared
| Severity: | INFORMATIONAL |
| Description: | Event log cleared. |
| Summary: | Adapter %s: Event log cleared (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10220: Event log wrapped
| Severity: | INFORMATIONAL |
| Description: | Event log wrapped. |
| Summary: | Adapter %s: Event log wrapped (Server %s) |
| Resolution: | Proceed with the following steps:
- Retry flash.
- Replace affected RAID controller.
|
| go to top | |
10224: Patrol Read rate changed
| Severity: | INFORMATIONAL |
| Description: | Patrol Read rate changed. |
| Summary: | Adapter %s: Patrol Read rate changed to %s percent (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10225: Reconstruction rate changed
| Severity: | INFORMATIONAL |
| Description: | Reconstruction rate changed. |
| Summary: | Adapter %s: Migration rate changed to %s percent (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10226: Shutdown command received
| Severity: | INFORMATIONAL |
| Description: | Shutdown command received. |
| Summary: | Adapter %s: Shutdown command received from host (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10227: Test event
| Severity: | INFORMATIONAL |
| Description: | Test event. |
| Summary: | Adapter %s: Test event: '%s' (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10228: Time established
| Severity: | INFORMATIONAL |
| Description: | Time established. |
| Summary: | Adapter %s: Time established as %s; (%s seconds since power on) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10229: User entered firmware debugger
| Severity: | INFORMATIONAL |
| Description: | User entered firmware debugger. |
| Summary: | Adapter %s: User entered firmware debugger (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10230: BGI corrected medium error
| Severity: | INFORMATIONAL |
| Description: | BGI corrected medium error. |
| Summary: | Adapter %s: BGI corrected medium error (logical drive %s at LBA %s on disk (%s) at LBA %s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace the RAID controller DIMM module (cache).
- If problem persists replace RAID controller.
|
| go to top | |
10234: BGI progress
| Severity: | INFORMATIONAL |
| Description: | BGI progress. |
| Summary: | Adapter %s: BGI progress on logical drive %s is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Restart Background initialization (BGI).
- Replace affected disk.
|
| go to top | |
10235: Policy change
| Severity: | INFORMATIONAL |
| Description: | Policy change. |
| Summary: | Adapter %s: Logical drive %s: %s changed (Server %s) |
| Resolution: | Proceed with the following steps:
- Restart Background initialization (BGI).
- Replace affected disk.
|
| go to top | |
10236: MDC corrected medium error
| Severity: | INFORMATIONAL |
| Description: | MDC corrected medium error. |
| Summary: | Adapter %s: MDC corrected medium error (logical drive %s at LBA %s on disk (%s) at LBA %s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Restart Background initialization (BGI).
- Replace affected disk.
|
| go to top | |
10238: Consistency check inconsistency logging disabled
| Severity: | INFORMATIONAL |
| Description: | Consistency check inconsistency logging disabled. |
| Summary: | Adapter %s: Consistency check logging disabled on logical drive %s (too many Inconsistencies) (Server %s) |
| Resolution: | Proceed with the following steps:
- Start consistency check again.
- If problem persists backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10239: Consistency check progress
| Severity: | INFORMATIONAL |
| Description: | Consistency check progress. |
| Summary: | Adapter %s: Consistency check progress on %s is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Start consistency check again.
- If problem persists backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10241: Initialization progress
| Severity: | INFORMATIONAL |
| Description: | Initialization progress. |
| Summary: | Adapter %s: Initialization progress on logical drive %s is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Start initialization again.
|
| go to top | |
10242: Fast initialization started
| Severity: | INFORMATIONAL |
| Description: | Fast initialization started. |
| Summary: | Adapter %s: Fast initialization started on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Start initialization again.
|
| go to top | |
10243: Full initialization started
| Severity: | INFORMATIONAL |
| Description: | Full initialization started. |
| Summary: | Adapter %s: Full initialization started on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Start initialization again.
|
| go to top | |
10244: Properties updated
| Severity: | INFORMATIONAL |
| Description: | Properties updated. |
| Summary: | Adapter %s: Logical drive %s: Property %s updated (Server %s) |
| Resolution: | Proceed with the following steps:
- Start initialization again.
|
| go to top | |
10246: Reconstruction progress
| Severity: | INFORMATIONAL |
| Description: | Reconstruction progress. |
| Summary: | Adapter %s: Migration progress on logical drive %s is %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10247: Reconstruction resumed
| Severity: | INFORMATIONAL |
| Description: | Reconstruction resumed. |
| Summary: | Adapter %s: Migration resumed on logical drive %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10249: State change from operational to operational
| Severity: | INFORMATIONAL |
| Description: | State change from operational to operational. |
| Summary: | Adapter %s: State change on logical drive %s from operational to operational (Server %s) |
| Resolution: | Proceed with the following steps:
- Check the RAID configuration and the event log for additional information.
- Backup data from affected logical drive.
|
| go to top | |
10252: Clear progress
| Severity: | INFORMATIONAL |
| Description: | Clear progress. |
| Summary: | Adapter %s: Clear progress on disk (%s) is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
- Verify that current RAID controller drivers are installed.
- Disconnect AC and wait 30 seconds before reconnect.
|
| go to top | |
10253: Clear started
| Severity: | INFORMATIONAL |
| Description: | Clear started. |
| Summary: | Adapter %s: Clear started on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
- Verify that current RAID controller drivers are installed.
- Disconnect AC and wait 30 seconds before reconnect.
|
| go to top | |
10254: Clear finished
| Severity: | INFORMATIONAL |
| Description: | Clear finished. |
| Summary: | Adapter %s: Clear finished on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
- Verify that current RAID controller drivers are installed.
- Disconnect AC and wait 30 seconds before reconnect.
|
| go to top | |
10256: Format complete
| Severity: | INFORMATIONAL |
| Description: | Format complete. |
| Summary: | Adapter %s: Format complete on disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10257: Format started
| Severity: | INFORMATIONAL |
| Description: | Format started. |
| Summary: | Adapter %s: Format started on disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10260: Patrol Read corrected medium error
| Severity: | INFORMATIONAL |
| Description: | Patrol Read corrected medium error. |
| Summary: | Adapter %s: Patrol Read corrected medium error on disk (%s) at LBA %s (Server %s) |
| Resolution: | Install supported disk. |
| go to top | |
10261: Patrol Read progress
| Severity: | INFORMATIONAL |
| Description: | Patrol Read progress. |
| Summary: | Adapter %s: Patrol Read progress on disk (%s) is %s (Server %s) |
| Resolution: | Install supported disk. |
| go to top | |
10266: Rebuild complete on logical drive
| Severity: | INFORMATIONAL |
| Description: | Rebuild complete on logical drive. |
| Summary: | Adapter %s: Rebuild complete on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10267: Rebuild complete on disk
| Severity: | INFORMATIONAL |
| Description: | Rebuild complete on disk. |
| Summary: | Adapter %s: Rebuild complete on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10268: Rebuild progress
| Severity: | INFORMATIONAL |
| Description: | Rebuild progress. |
| Summary: | Adapter %s: Rebuild progress on disk (%s) is %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10269: Rebuild resumed
| Severity: | INFORMATIONAL |
| Description: | Rebuild resumed. |
| Summary: | Adapter %s: Rebuild resumed on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10270: Rebuild automatically started
| Severity: | INFORMATIONAL |
| Description: | Rebuild automatically started. |
| Summary: | Adapter %s: Rebuild automatically started on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10274: Corrected medium error during recovery
| Severity: | INFORMATIONAL |
| Description: | Corrected medium error during recovery. |
| Summary: | Adapter %s: Corrected medium error during recovery on disk (%s) at LBA %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10276: Unexpected sense
| Severity: | INFORMATIONAL |
| Description: | Unexpected sense. |
| Summary: | Adapter %s: Unexpected sense: Disk (%s), Key/ASC/ASCQ: %s: %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10277: State change from available to available
| Severity: | INFORMATIONAL |
| Description: | State change from available to available. |
| Summary: | Adapter %s: State change on disk (%s) from available to available (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10278: State change by user from available to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from available to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to available (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10280: Redundant path restored
| Severity: | INFORMATIONAL |
| Description: | Redundant path restored. |
| Summary: | Adapter %s: Redundant path to disk (%s) restored (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10298: BBU present
| Severity: | INFORMATIONAL |
| Description: | BBU present. |
| Summary: | Adapter %s: BBU present (Server %s) |
| Resolution: | Initiate consistency check (e.g. via ServerView RAID Manager). |
| go to top | |
10299: BBU not present
| Severity: | INFORMATIONAL |
| Description: | BBU not present. |
| Summary: | Adapter %s: BBU not present (Server %s) |
| Resolution: | If the system does not have a BBU this is for information only. If the system does have a BBU replace the BBU. |
| go to top | |
10300: New BBU detected
| Severity: | INFORMATIONAL |
| Description: | New BBU detected. |
| Summary: | Adapter %s: New BBU detected (Server %s) |
| Resolution: | If the system does not have a BBU this is for information only. If the system does have a BBU replace the BBU. |
| go to top | |
10301: BBU has been replaced
| Severity: | INFORMATIONAL |
| Description: | BBU has been replaced. |
| Summary: | Adapter %s: BBU has been replaced (Server %s) |
| Resolution: | If the system does not have a BBU this is for information only. If the system does have a BBU replace the BBU. |
| go to top | |
10302: BBU temperature is normal
| Severity: | INFORMATIONAL |
| Description: | BBU temperature is normal. |
| Summary: | Adapter %s: BBU temperature is normal (Server %s) |
| Resolution: | If the system does not have a BBU this is for information only. If the system does have a BBU replace the BBU. |
| go to top | |
10304: BBU relearn started
| Severity: | INFORMATIONAL |
| Description: | BBU relearn started. |
| Summary: | Adapter %s: BBU relearn started (Server %s) |
| Resolution: | If the error message occurs right after replacement of the BBU it can be safely ignored. The situation can occur due to the insufficient BBU charge. If the error message occurs during regular operation replace the BBU. |
| go to top | |
10305: BBU relearn in progress
| Severity: | INFORMATIONAL |
| Description: | BBU relearn in progress. |
| Summary: | Adapter %s: BBU relearn in progress (Server %s) |
| Resolution: | If the error message occurs right after replacement of the BBU it can be safely ignored. The situation can occur due to the insufficient BBU charge. If the error message occurs during regular operation replace the BBU. |
| go to top | |
10306: BBU relearn finished
| Severity: | INFORMATIONAL |
| Description: | BBU relearn finished. |
| Summary: | Adapter %s: BBU relearn finished (Server %s) |
| Resolution: | If the error message occurs right after replacement of the BBU it can be safely ignored. The situation can occur due to the insufficient BBU charge. If the error message occurs during regular operation replace the BBU. |
| go to top | |
10308: BBU relearn pending
| Severity: | INFORMATIONAL |
| Description: | BBU relearn pending. |
| Summary: | Adapter %s: BBU relearn pending: BBU is under charge (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10309: BBU relearn postponed
| Severity: | INFORMATIONAL |
| Description: | BBU relearn postponed. |
| Summary: | Adapter %s: BBU relearn postponed (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10310: BBU relearn will start in 4 days
| Severity: | INFORMATIONAL |
| Description: | BBU relearn will start in 4 days. |
| Summary: | Adapter %s: BBU relearn will start in 4 days (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10311: BBU relearn will start in 2 days
| Severity: | INFORMATIONAL |
| Description: | BBU relearn will start in 2 days. |
| Summary: | Adapter %s: BBU relearn will start in 2 days (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10312: BBU relearn will start in 1 day
| Severity: | INFORMATIONAL |
| Description: | BBU relearn will start in 1 day. |
| Summary: | Adapter %s: BBU relearn will start in 1 day (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10313: BBU relearn will start in 5 hours
| Severity: | INFORMATIONAL |
| Description: | BBU relearn will start in 5 hours. |
| Summary: | Adapter %s: BBU Relearn will start in 5 hours (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10315: Enclosure (SES) discovered
| Severity: | INFORMATIONAL |
| Description: | Enclosure (SES) discovered. |
| Summary: | Adapter %s: Enclosure (SES) discovered on %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10316: Enclosure (SAF-TE) discovered
| Severity: | INFORMATIONAL |
| Description: | Enclosure (SAF-TE) discovered. |
| Summary: | Adapter %s: Enclosure (SAF-TE) discovered on %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10318: Enclosure communication restored
| Severity: | INFORMATIONAL |
| Description: | Enclosure communication restored. |
| Summary: | Adapter %s: Enclosure %s communication restored (Server %s) |
| Resolution: | Proceed with the following steps:
- Check data cable(s) to enclosure.
- Check if enclosure is running.
|
| go to top | |
10319: Enclosure fan inserted
| Severity: | INFORMATIONAL |
| Description: | Enclosure fan inserted. |
| Summary: | Adapter %s: Enclosure %s fan %s inserted (Server %s) |
| Resolution: | Proceed with the following steps:
- Check data cable(s) to enclosure.
- Check if enclosure is running.
|
| go to top | |
10322: Enclosure I/O module inserted
| Severity: | INFORMATIONAL |
| Description: | Enclosure I/O module inserted. |
| Summary: | Adapter %s: Enclosure %s I/O module %s inserted (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10333: Enclosure (SES) hotplug not supported
| Severity: | INFORMATIONAL |
| Description: | Enclosure (SES) hotplug not supported. |
| Summary: | Adapter %s: Enclosure (SES) hot plug on %s was detected, but is not supported (Server %s) |
| Resolution: | Check your disk configuration within enclosure. |
| go to top | |
10334: Clustering enabled
| Severity: | INFORMATIONAL |
| Description: | Clustering enabled. |
| Summary: | Adapter %s: Clustering enabled (Server %s) |
| Resolution: | Check your disk configuration within enclosure. |
| go to top | |
10335: Clustering disabled
| Severity: | INFORMATIONAL |
| Description: | Clustering disabled. |
| Summary: | Adapter %s: Clustering disabled (Server %s) |
| Resolution: | Check your disk configuration within enclosure. |
| go to top | |
10337: BBU enabled; changing Write-through virtual disks to Write-back
| Severity: | INFORMATIONAL |
| Description: | BBU enabled; changing Write-through virtual disks to Write-back. |
| Summary: | Adapter %s: BBU enabled; changing Write-through logical drives to Write-back (Server %s) |
| Resolution: | Check your disk configuration. |
| go to top | |
10339: Bad block table 80 percent full
| Severity: | INFORMATIONAL |
| Description: | Bad block table 80 percent full. |
| Summary: | Adapter %s: Bad block table on disk (%s) is 80 percent full (Server %s) |
| Note: | Only informational during recalibration process. |
| Resolution: | Proceed with the following steps:
- Check connection between BBU data/power cable and RAID controller.
- Check version of RAID controller/iRMC firmware, and BIOS.
- If problem persists replace BBU.
|
| go to top | |
10348: Enclosure power supply cable inserted
| Severity: | INFORMATIONAL |
| Description: | Enclosure power supply cable inserted. |
| Summary: | Adapter %s: Enclosure %s power supply %s cable inserted (Server %s) |
| Resolution: | Check the enclosure power cable(s). |
| go to top | |
10349: Enclosure fan returned to normal
| Severity: | INFORMATIONAL |
| Description: | Enclosure fan returned to normal. |
| Summary: | Adapter %s: Enclosure %s fan %s returned to normal (Server %s) |
| Resolution: | Check the enclosure power cable(s). |
| go to top | |
10350: BBU retention started on previous Boot
| Severity: | INFORMATIONAL |
| Description: | BBU retention started on previous Boot. |
| Summary: | Adapter %s: BBU retention started on previous boot (Server %s) |
| Resolution: | Check the enclosure power cable(s). |
| go to top | |
10351: BBU retention test passed
| Severity: | INFORMATIONAL |
| Description: | BBU retention test passed. |
| Summary: | Adapter %s: BBU retention test passed (Server %s) |
| Resolution: | Check the enclosure power cable(s). |
| go to top | |
10353: Retention test started on previous reboot
| Severity: | INFORMATIONAL |
| Description: | Retention test started on previous reboot. |
| Summary: | Adapter %s: Retention test started on previous reboot (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10354: NVRAM retention test passed
| Severity: | INFORMATIONAL |
| Description: | NVRAM retention test passed. |
| Summary: | Adapter %s: NVRAM retention test passed (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10356: Self check test finished successfully
| Severity: | INFORMATIONAL |
| Description: | Self check test finished successfully. |
| Summary: | Adapter %s: %s test finished %s passes successfully (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10358: Self check diagnostics finished
| Severity: | INFORMATIONAL |
| Description: | Self check diagnostics finished. |
| Summary: | Adapter %s: Self-check diagnostics finished (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10359: Foreign configuration detected
| Severity: | INFORMATIONAL |
| Description: | Foreign configuration detected. |
| Summary: | Adapter %s: Foreign configuration detected (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10360: Foreign configuration imported
| Severity: | INFORMATIONAL |
| Description: | Foreign configuration imported. |
| Summary: | Adapter %s: Foreign configuration imported (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10361: Foreign configuration cleared
| Severity: | INFORMATIONAL |
| Description: | Foreign configuration cleared. |
| Summary: | Adapter %s: Foreign configuration cleared (Server %s) |
| Resolution: | Note: In general additional error messages should occur. If there are no other actions defined call your local Fujitsu Helpdesk. |
| go to top | |
10365: SAS wide port restored link on PHY
| Severity: | INFORMATIONAL |
| Description: | SAS wide port restored link on PHY. |
| Summary: | Adapter %s: SAS wide port %s restored link on PHY %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10368: Controller hot plug detected
| Severity: | INFORMATIONAL |
| Description: | Controller hot plug detected. |
| Summary: | Adapter %s: Adapter hot plug detected (Server %s) |
| Resolution: | If the problem occurs repeatedly replace the disk during next maintenance. |
| go to top | |
10369: Enclosure temperature sensor differential detected
| Severity: | INFORMATIONAL |
| Description: | Enclosure temperature sensor differential detected. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s differential detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10370: Disk test cannot start. No qualifying disks found
| Severity: | INFORMATIONAL |
| Description: | Disk test cannot start. No qualifying disks found. |
| Summary: | Adapter %s: Disk test cannot start. No qualifying disks found (Server %s) |
| Resolution: | For information only. |
| go to top | |
10371: Time duration provided by host is not sufficient for self-checking
| Severity: | INFORMATIONAL |
| Description: | Time duration provided by host is not sufficient for self-checking. |
| Summary: | Adapter %s: Time duration provided by host is not sufficient for self-checking (Server %s) |
| Resolution: | For information only. |
| go to top | |
10372: Marked as missing
| Severity: | INFORMATIONAL |
| Description: | Marked as missing. |
| Summary: | Adapter %s: Disk (%s) on array %s row %s marked as missing (Server %s) |
| Resolution: | For information only. |
| go to top | |
10373: Replaced missing
| Severity: | INFORMATIONAL |
| Description: | Replaced missing. |
| Summary: | Adapter %s: Disk (%s) replaced missing on array %s row %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10374: Enclosure temperature sensor returned to normal
| Severity: | INFORMATIONAL |
| Description: | Enclosure temperature sensor returned to normal. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s returned to normal (Server %s) |
| Resolution: | For information only. |
| go to top | |
10375: Enclosure firmware download in progress
| Severity: | INFORMATIONAL |
| Description: | Enclosure firmware download in progress. |
| Summary: | Adapter %s: Enclosure %s firmware download in progress (Server %s) |
| Resolution: | For information only. |
| go to top | |
10383: BBU charging complete
| Severity: | INFORMATIONAL |
| Description: | BBU charging complete. |
| Summary: | Adapter %s: BBU charging complete (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10384: Enclosure fan speed changed
| Severity: | INFORMATIONAL |
| Description: | Enclosure fan speed changed. |
| Summary: | Adapter %s: Enclosure %s fan %s speed changed (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10385: Dedicated spare imported as global due to missing arrays
| Severity: | INFORMATIONAL |
| Description: | Dedicated spare imported as global due to missing arrays. |
| Summary: | Adapter %s: Dedicated hot spare (%s) imported as global due to missing arrays (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10386: Disk rebuild not possible as SAS/SATA mixing is not supported in an array
| Severity: | INFORMATIONAL |
| Description: | Disk rebuild not possible as SAS/SATA mixing is not supported in an array. |
| Summary: | Adapter %s: Disk (%s) rebuild not possible as SAS/SATA mixing is not supported in an array (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10387: I/O module has been rebooted as part of enclosure firmware download
| Severity: | INFORMATIONAL |
| Description: | I/O module has been rebooted as part of enclosure firmware download. |
| Summary: | Adapter %s: I/O module %s has been rebooted as part of enclosure firmware download. It will be unavailable until reboot completes (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10390: Coercion mode changed
| Severity: | INFORMATIONAL |
| Description: | Coercion mode changed. |
| Summary: | Adapter %s: Coercion mode changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10391: BBU automatic Learn mode changed
| Severity: | INFORMATIONAL |
| Description: | BBU automatic Learn mode changed. |
| Summary: | Adapter %s: BBU automatic learn mode changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10392: BBU automatic learn period changed
| Severity: | INFORMATIONAL |
| Description: | BBU automatic learn period changed. |
| Summary: | Adapter %s: BBU automatic learn period changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10393: BBU learn delay interval changed
| Severity: | INFORMATIONAL |
| Description: | BBU learn delay interval changed. |
| Summary: | Adapter %s: BBU learn delay interval changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10394: BBU next learn time changed
| Severity: | INFORMATIONAL |
| Description: | BBU next learn time changed. |
| Summary: | Adapter %s: BBU next learn time changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10395: Max. disk count for Patrol Read changed
| Severity: | INFORMATIONAL |
| Description: | Max. disk count for Patrol Read changed. |
| Summary: | Adapter %s: Max. disk count for Patrol Read changed to %s (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10396: Continuous patrolling enabled
| Severity: | INFORMATIONAL |
| Description: | Continuous patrolling enabled. |
| Summary: | Adapter %s: Continuous patrolling enabled (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10397: Continuous patrolling disabled
| Severity: | INFORMATIONAL |
| Description: | Continuous patrolling disabled. |
| Summary: | Adapter %s: Continuous patrolling disabled (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10399: Logical drive disabled because RAID-5 not supported
| Severity: | INFORMATIONAL |
| Description: | Logical drive disabled because RAID-5 not supported. |
| Summary: | Adapter %s: Logical drive %s disabled because RAID-5 is not supported by this RAID key (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists replace affected disk.
|
| go to top | |
10400: Logical drive disabled because RAID-6 not supported
| Severity: | INFORMATIONAL |
| Description: | Logical drive disabled because RAID-6 not supported. |
| Summary: | Adapter %s: Logical drive %s disabled because RAID-6 is not supported by this RAID key (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate second consistency check (MDC).
- If problem persists replace affected disk.
|
| go to top | |
10403: Rebuild rate changed
| Severity: | INFORMATIONAL |
| Description: | Rebuild rate changed. |
| Summary: | Adapter %s: Rebuild rate changed to %s percent (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10404: Consistency check rate changed
| Severity: | INFORMATIONAL |
| Description: | Consistency check rate changed. |
| Summary: | Adapter %s: Consistency check rate changed to %s percent (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10405: SMART poll interval changed
| Severity: | INFORMATIONAL |
| Description: | SMART poll interval changed. |
| Summary: | Adapter %s: SMART poll interval changed to %s s (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10406: MDC started on logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC started on logical drive. |
| Summary: | Adapter %s: MDC started on logical drive %s (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10407: MDC finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC finished on logical drive. |
| Summary: | Adapter %s: MDC finished on logical drive %s (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10410: MDC suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC suspended on logical drive. |
| Summary: | Adapter %s: MDC suspended on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10411: MDC started on uninitialized logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC started on uninitialized logical drive. |
| Summary: | Adapter %s: MDC started on uninitialized logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10415: State change from degraded to operational
| Severity: | INFORMATIONAL |
| Description: | State change from degraded to operational. |
| Summary: | Adapter %s: State change on logical drive %s from degraded to operational (Server %s) |
| Resolution: | Proceed with the following steps:
- Check version of RAID controller/iRMC firmware, and BIOS.
|
| go to top | |
10419: State change from partially degraded to operational
| Severity: | INFORMATIONAL |
| Description: | State change from partially degraded to operational. |
| Summary: | Adapter %s: State change on logical drive %s from partially degraded to operational (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disks.
- The array has to be recreated. Note: Data loss is probable.
|
| go to top | |
10423: State change from failed to operational
| Severity: | INFORMATIONAL |
| Description: | State change from failed to operational. |
| Summary: | Adapter %s: State change on logical drive %s from failed to operational (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disks.
- The array has to be recreated. Note: Data loss is probable.
|
| go to top | |
10428: State change by user from available to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from available to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10429: State change by user from available to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from available to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10430: State change by user from available to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from available to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10431: State change by user from failed to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from failed to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10433: State change by user from failed to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from failed to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10434: State change by user from failed to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from failed to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10435: State change by user from failed to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from failed to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10436: State change by user from hot spare to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from hot spare to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10438: State change by user from hot spare to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from hot spare to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10439: State change by user from hot spare to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from hot spare to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10440: State change by user from hot spare to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from hot spare to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10441: State change by user from rebuilding to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from rebuilding to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10443: State change by user from rebuilding to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from rebuilding to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10444: State change by user from rebuilding to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from rebuilding to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10445: State change by user from rebuilding to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from rebuilding to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10446: State change by user from operational to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from operational to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10448: State change by user from operational to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from operational to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10449: State change by user from operational to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from operational to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10450: State change by user from operational to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from operational to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10452: State change from available to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from available to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from available to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10453: State change from available to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from available to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from available to rebuilding (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10454: State change from available to operational
| Severity: | INFORMATIONAL |
| Description: | State change from available to operational. |
| Summary: | Adapter %s: State change on disk (%s) from available to operational (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10455: State change from failed to available
| Severity: | INFORMATIONAL |
| Description: | State change from failed to available. |
| Summary: | Adapter %s: State change on disk (%s) from failed to available (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10457: State change from failed to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from failed to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from failed to hot spare (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10458: State change from failed to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from failed to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from failed to rebuilding (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10459: State change from failed to operational
| Severity: | INFORMATIONAL |
| Description: | State change from failed to operational. |
| Summary: | Adapter %s: State change on disk (%s) from failed to operational (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10460: State change from hot spare to available
| Severity: | INFORMATIONAL |
| Description: | State change from hot spare to available. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to available (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10462: State change from hot spare to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from hot spare to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10463: State change from hot spare to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from hot spare to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to rebuilding (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10464: State change from hot spare to operational
| Severity: | INFORMATIONAL |
| Description: | State change from hot spare to operational. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to operational (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10465: State change from rebuilding to available
| Severity: | INFORMATIONAL |
| Description: | State change from rebuilding to available. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to available (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10467: State change from rebuilding to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from rebuilding to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to hot spare (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10468: State change from rebuilding to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from rebuilding to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to rebuilding (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10469: State change from rebuilding to operational
| Severity: | INFORMATIONAL |
| Description: | State change from rebuilding to operational. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to operational (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10470: State change from operational to available
| Severity: | INFORMATIONAL |
| Description: | State change from operational to available. |
| Summary: | Adapter %s: State change on disk (%s) from operational to available (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually initiate a second rebuild (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10472: State change from operational to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from operational to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from operational to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10473: State change from operational to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from operational to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from operational to rebuilding (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10474: State change from operational to operational
| Severity: | INFORMATIONAL |
| Description: | State change from operational to operational. |
| Summary: | Adapter %s: State change on disk (%s) from operational to operational (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10478: Disk appeared new after reboot
| Severity: | INFORMATIONAL |
| Description: | Disk appeared new after reboot. |
| Summary: | Adapter %s: Disk (%s) appeared new after reboot (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10479: Logical drive appeared new after reboot
| Severity: | INFORMATIONAL |
| Description: | Logical drive appeared new after reboot. |
| Summary: | Adapter %s: Logical drive %s appeared new after reboot (Server %s) |
| Resolution: | Check your RAID configuration. |
| go to top | |
10483: Package version
| Severity: | INFORMATIONAL |
| Description: | Package version. |
| Summary: | Adapter %s: Package version %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10484: Media verification corrected error
| Severity: | INFORMATIONAL |
| Description: | Media verification corrected error. |
| Summary: | Adapter %s: Media verification corrected error (logical drive %s at LBA %s on disk (%s) at LBA %s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10489: State change by user from offline to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from offline to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10491: State change by user from offline to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from offline to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10493: State change by user from offline to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from offline to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10494: State change by user from offline to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from offline to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10499: State change from offline to available
| Severity: | INFORMATIONAL |
| Description: | State change from offline to available. |
| Summary: | Adapter %s: State change on disk (%s) from offline to available (Server %s) |
| Resolution: | Proceed with the following steps:
- Manually set the disk to hot spare again (e.g. via ServerView RAID Manager).
- If problem persists replace affected disk.
|
| go to top | |
10501: State change from offline to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from offline to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from offline to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10503: State change from offline to operational
| Severity: | INFORMATIONAL |
| Description: | State change from offline to operational. |
| Summary: | Adapter %s: State change on disk (%s) from offline to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10504: State change from offline to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from offline to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from offline to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10507: Data in cache flushed during power up
| Severity: | INFORMATIONAL |
| Description: | Data in cache flushed during power up. |
| Summary: | Adapter %s: Data in cache flushed during power up (Server %s) |
| Note: | Only informational if status change was forced by user otherwise: |
| Resolution: | Proceed with the following steps:
|
| go to top | |
10509: Rebuild resumed on disk
| Severity: | INFORMATIONAL |
| Description: | Rebuild resumed on disk. |
| Summary: | Adapter %s: Rebuild resumed on disk (%s) (Server %s) |
| Resolution: | If the problem occurs repeatedly call your local Fujitsu Helpdesk. |
| go to top | |
10510: Automatic rebuild started on logical drive
| Severity: | INFORMATIONAL |
| Description: | Automatic rebuild started on logical drive. |
| Summary: | Adapter %s: Automatic rebuild started on logical drive %s (Server %s) |
| Resolution: | If the problem occurs repeatedly call your local Fujitsu Helpdesk. |
| go to top | |
10511: BGI restarted on logical drive
| Severity: | INFORMATIONAL |
| Description: | BGI restarted on logical drive. |
| Summary: | Adapter %s: BGI restarted on logical drive %s (Server %s) |
| Resolution: | If the problem occurs repeatedly call your local Fujitsu Helpdesk. |
| go to top | |
10513: Rebuild on logical drive resumed
| Severity: | INFORMATIONAL |
| Description: | Rebuild on logical drive resumed. |
| Summary: | Adapter %s: Rebuild on logical drive %s resumed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10519: SAS port restored link
| Severity: | INFORMATIONAL |
| Description: | SAS port restored link. |
| Summary: | Adapter %s: SAS port %s restored link (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10520: Cache mode changed to Write-back
| Severity: | INFORMATIONAL |
| Description: | Cache mode changed to Write-back. |
| Summary: | Adapter %s: Cache mode changed to Write-back (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10521: Cache mode changed to Write-through
| Severity: | INFORMATIONAL |
| Description: | Cache mode changed to Write-through. |
| Summary: | Adapter %s: Cache mode changed to Write-through (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10525: Connector is active
| Severity: | INFORMATIONAL |
| Description: | Connector is active. |
| Summary: | Adapter %s: Connector %s is active (Server %s) |
| Note: | Only parts of your config were imported. |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10527: Adapter appeared new after reboot
| Severity: | INFORMATIONAL |
| Description: | Adapter appeared new after reboot. |
| Summary: | Adapter %s: Adapter appeared new after reboot (Server %s) |
| Note: | Only informational if controller was removed by user otherwise: |
| Resolution: | Proceed with the following steps:
- Unplug affected controller, wait 30 seconds, reinsert it.
- If problem persists replace affected controller.
- If problem persists replace mainboard.
|
| go to top | |
10531: MDC finished with correctable errors on logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC finished with correctable errors on logical drive. |
| Summary: | Adapter %s: MDC finished with %s correctable errors on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10533: Error counters reset on disk
| Severity: | INFORMATIONAL |
| Description: | Error counters reset on disk. |
| Summary: | Adapter %s: Error counters reset on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Backup data from affected logical drive.
- Delete and recreate affected logical drive.
- Restore data.
|
| go to top | |
10535: Board revision
| Severity: | INFORMATIONAL |
| Description: | Board revision. |
| Summary: | Adapter %s: Board revision %s (Server %s) |
| Resolution: | Check your adapter properties (e.g. via ServerView RAID Manager). |
| go to top | |
10541: Medium error corrected on logical drive
| Severity: | INFORMATIONAL |
| Description: | Medium error corrected on logical drive. |
| Summary: | Adapter %s: Medium error corrected on logical drive %s at LBA %s (Server %s) |
| Resolution: | Check for additional error messages for affected disk. |
| go to top | |
10545: Copyback started on disk from disk
| Severity: | INFORMATIONAL |
| Description: | Copyback started on disk from disk. |
| Summary: | Adapter %s: Copyback started on disk (%s) from disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10546: Copyback aborted on disk from disk
| Severity: | INFORMATIONAL |
| Description: | Copyback aborted on disk from disk. |
| Summary: | Adapter %s: Copyback aborted on disk (%s) from disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10547: Copyback complete on disk from disk
| Severity: | INFORMATIONAL |
| Description: | Copyback complete on disk from disk. |
| Summary: | Adapter %s: Copyback complete on disk (%s) from disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10548: Copyback progress
| Severity: | INFORMATIONAL |
| Description: | Copyback progress. |
| Summary: | Adapter %s: Copyback progress on disk (%s) is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10549: Copyback resumed on disk
| Severity: | INFORMATIONAL |
| Description: | Copyback resumed on disk. |
| Summary: | Adapter %s: Copyback resumed on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10550: Copyback automatically started on disk
| Severity: | INFORMATIONAL |
| Description: | Copyback automatically started on disk. |
| Summary: | Adapter %s: Copyback automatically started on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10553: BBU FRU
| Severity: | INFORMATIONAL |
| Description: | BBU FRU. |
| Summary: | Adapter %s: BBU FRU is %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10554: Disk FRU
| Severity: | INFORMATIONAL |
| Description: | Disk FRU. |
| Summary: | Adapter %s: Disk (%s) FRU is %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10555: Adapter hardware revision ID
| Severity: | INFORMATIONAL |
| Description: | Adapter hardware revision ID. |
| Summary: | Adapter %s: Adapter hardware revision ID %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10557: BIOS continue on error enabled
| Severity: | INFORMATIONAL |
| Description: | BIOS continue on error enabled. |
| Summary: | Adapter %s: BIOS continue on error enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10558: BIOS continue on error disabled
| Severity: | INFORMATIONAL |
| Description: | BIOS continue on error disabled. |
| Summary: | Adapter %s: BIOS continue on error disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10559: Additional information for failed disk
| Severity: | INFORMATIONAL |
| Description: | Additional information for failed disk. |
| Summary: | Adapter %s: Additional information for failed disk (%s) - firmware version: %s, serial number %s, first use: %s, total running time: %s days (Server %s) |
| Resolution: | For information only. |
| go to top | |
10560: Reread disk information
| Severity: | INFORMATIONAL |
| Description: | Reread disk information. |
| Summary: | Adapter %s: If the logical size of logical drive %s has changed use appropriate operating system tool to reread disk information (Server %s) |
| Resolution: | For information only. |
| go to top | |
10561: Enclosure device exposure changed
| Severity: | INFORMATIONAL |
| Description: | Enclosure device exposure changed. |
| Summary: | Adapter %s: Enclosure device exposure changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10562: Abort consistency check on error changed
| Severity: | INFORMATIONAL |
| Description: | Abort consistency check on error changed. |
| Summary: | Adapter %s: Abort consistency check on error changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10563: Abort MDC on error changed
| Severity: | INFORMATIONAL |
| Description: | Abort MDC on error changed. |
| Summary: | Adapter %s: Abort MDC on error changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10564: Redundant path restored
| Severity: | INFORMATIONAL |
| Description: | Redundant path restored. |
| Summary: | Adapter %s: Redundant path restored for disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10566: Redundant enclosure inserted
| Severity: | INFORMATIONAL |
| Description: | Redundant enclosure inserted. |
| Summary: | Adapter %s: Redundant enclosure I/O module %s inserted for I/O module %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10569: Copyback aborted by user
| Severity: | INFORMATIONAL |
| Description: | Copyback aborted by user. |
| Summary: | Adapter %s: Copyback aborted by user on disk (%s) from disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10573: Redundancy building started on disk
| Severity: | INFORMATIONAL |
| Description: | Redundancy building started on disk. |
| Summary: | Adapter %s: Redundancy building started on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10574: Redundancy building finished on disk
| Severity: | INFORMATIONAL |
| Description: | Redundancy building finished on disk. |
| Summary: | Adapter %s: Redundancy building finished on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10577: Redundancy building suspended on disk
| Severity: | INFORMATIONAL |
| Description: | Redundancy building suspended on disk. |
| Summary: | Adapter %s: Redundancy building suspended on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10578: Disk power management idle mode enabled
| Severity: | INFORMATIONAL |
| Description: | Disk power management idle mode enabled. |
| Summary: | Adapter %s: Disk (%s) power management idle mode enabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10579: Disk power management idle mode disabled
| Severity: | INFORMATIONAL |
| Description: | Disk power management idle mode disabled. |
| Summary: | Adapter %s: Disk (%s) power management idle mode disabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10580: Disk power management idle condition timer changed
| Severity: | INFORMATIONAL |
| Description: | Disk power management idle condition timer changed. |
| Summary: | Adapter %s: Disk (%s) power management idle condition timer changed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10581: Disk power management standby mode enabled
| Severity: | INFORMATIONAL |
| Description: | Disk power management standby mode enabled. |
| Summary: | Adapter %s: Disk (%s) power management standby mode enabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10582: Disk power management standby mode disabled
| Severity: | INFORMATIONAL |
| Description: | Disk power management standby mode disabled. |
| Summary: | Adapter %s: Disk (%s) power management standby mode disabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10583: Disk power management standby condition timer changed
| Severity: | INFORMATIONAL |
| Description: | Disk power management standby condition timer changed. |
| Summary: | Adapter %s: Disk (%s) power management standby condition timer changed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10584: Copyback cannot be started as disk is too small for disk
| Severity: | INFORMATIONAL |
| Description: | Copyback cannot be started as disk is too small for disk. |
| Summary: | Adapter %s: Copyback cannot be started as disk (%s) is too small for disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10585: Copyback cannot be started on disk from disk as SAS/SATA mixing is not supported in an array
| Severity: | INFORMATIONAL |
| Description: | Copyback cannot be started on disk from disk as SAS/SATA mixing is not supported in an array. |
| Summary: | Adapter %s: Copyback cannot be started on disk (%s) from disk (%s) as SAS/SATA mixing is not supported in an array (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10586: Firmware update started on disk
| Severity: | INFORMATIONAL |
| Description: | Firmware update started on disk. |
| Summary: | Adapter %s: Firmware update started on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10587: Firmware update completed on disk
| Severity: | INFORMATIONAL |
| Description: | Firmware update completed on disk. |
| Summary: | Adapter %s: Firmware update completed on disk (%s) (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10590: Adapter properties changed
| Severity: | INFORMATIONAL |
| Description: | Adapter properties changed. |
| Summary: | Adapter %s: Adapter properties changed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10591: Patrol Read properties changed
| Severity: | INFORMATIONAL |
| Description: | Patrol Read properties changed. |
| Summary: | Adapter %s: Patrol Read properties changed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10592: MDC schedule properties changed
| Severity: | INFORMATIONAL |
| Description: | MDC schedule properties changed. |
| Summary: | Adapter %s: MDC schedule properties changed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10593: BBU properties changed
| Severity: | INFORMATIONAL |
| Description: | BBU properties changed. |
| Summary: | Adapter %s: BBU properties changed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10594: MDC resumed on logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC resumed on logical drive. |
| Summary: | Adapter %s: MDC resumed on logical drive %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10595: Spindown mode enabled
| Severity: | INFORMATIONAL |
| Description: | Spindown mode enabled. |
| Summary: | Adapter %s: Spindown mode enabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10596: Spindown mode disabled
| Severity: | INFORMATIONAL |
| Description: | Spindown mode disabled. |
| Summary: | Adapter %s: Spindown mode disabled (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10597: Spindown delay changed
| Severity: | INFORMATIONAL |
| Description: | Spindown delay changed. |
| Summary: | Adapter %s: Spindown delay changed to %s seconds (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10598: Spinup delay changed
| Severity: | INFORMATIONAL |
| Description: | Spinup delay changed. |
| Summary: | Adapter %s: Spinup delay changed to %s seconds (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10599: Redundancy build rate changed
| Severity: | INFORMATIONAL |
| Description: | Redundancy build rate changed. |
| Summary: | Adapter %s: Redundancy build rate changed to %s percent (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10600: Copyback rate changed
| Severity: | INFORMATIONAL |
| Description: | Copyback rate changed. |
| Summary: | Adapter %s: Copyback rate changed to %s percent (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10602: Disk security key created
| Severity: | INFORMATIONAL |
| Description: | Disk security key created. |
| Summary: | Adapter %s: Disk security key created (Server %s) |
| Resolution: | Initiate manual learn cycle as automatic learn is not enabled. |
| go to top | |
10603: Disk security key backed up
| Severity: | INFORMATIONAL |
| Description: | Disk security key backed up. |
| Summary: | Adapter %s: Disk security key backed up (Server %s) |
| Resolution: | Initiate manual learn cycle as automatic learn is not enabled. |
| go to top | |
10604: Disk security key from escrow, verified
| Severity: | INFORMATIONAL |
| Description: | Disk security key from escrow, verified. |
| Summary: | Adapter %s: Disk security key from escrow, verified (Server %s) |
| Resolution: | Initiate manual learn cycle as automatic learn is not enabled. |
| go to top | |
10605: Disk security key changed
| Severity: | INFORMATIONAL |
| Description: | Disk security key changed. |
| Summary: | Adapter %s: Disk security key changed (Server %s) |
| Resolution: | Initiate manual learn cycle as automatic learn is not enabled. |
| go to top | |
10608: Disk security key destroyed
| Severity: | INFORMATIONAL |
| Description: | Disk security key destroyed. |
| Summary: | Adapter %s: Disk security key destroyed (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10610: Logical drive is now secured
| Severity: | INFORMATIONAL |
| Description: | Logical drive is now secured. |
| Summary: | Adapter %s: Logical drive %s is now secured (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10612: Disk security activated
| Severity: | INFORMATIONAL |
| Description: | Disk security activated. |
| Summary: | Adapter %s: Disk (%s) security activated (Server %s) |
| Resolution: | For information only. |
| go to top | |
10613: Disk security disabled
| Severity: | INFORMATIONAL |
| Description: | Disk security disabled. |
| Summary: | Adapter %s: Disk (%s) security disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10614: Disk is reprovisioned
| Severity: | INFORMATIONAL |
| Description: | Disk is reprovisioned. |
| Summary: | Adapter %s: Disk (%s) is reprovisioned (Server %s) |
| Resolution: | For information only. |
| go to top | |
10615: Disk security key changed
| Severity: | INFORMATIONAL |
| Description: | Disk security key changed. |
| Summary: | Adapter %s: Disk (%s) security key changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10619: Adapter cache discarded by user for logical drives
| Severity: | INFORMATIONAL |
| Description: | Adapter cache discarded by user for logical drives. |
| Summary: | Adapter %s: Adapter cache discarded by user for logical drives (Server %s) |
| Resolution: | Check error messages for related logical drives and resolve problems. |
| go to top | |
10620: Adapter cache destaged for logical drive
| Severity: | INFORMATIONAL |
| Description: | Adapter cache destaged for logical drive. |
| Summary: | Adapter %s: Adapter cache destaged for logical drive %s (Server %s) |
| Resolution: | Check error messages for related logical drives and resolve problems. |
| go to top | |
10624: Complete RAID configuration written to file on the server
| Severity: | INFORMATIONAL |
| Description: | Complete RAID configuration written to file on the server. |
| Summary: | Complete RAID configuration written to file '%s' on the server (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10628: Bad block table threshold exceeded
| Severity: | INFORMATIONAL |
| Description: | Bad block table threshold exceeded. |
| Summary: | Adapter %s: Bad block table of disk (%s) threshold exceeded; table is about to overflow (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10629: Bad block table cleared
| Severity: | INFORMATIONAL |
| Description: | Bad block table cleared. |
| Summary: | Adapter %s: Bad block table of disk (%s) cleared (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10634: BGI started due to adapter exchange
| Severity: | INFORMATIONAL |
| Description: | BGI started due to adapter exchange. |
| Summary: | Adapter %s: BGI started due to adapter exchange (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10640: Adapter was exchanged
| Severity: | INFORMATIONAL |
| Description: | Adapter was exchanged. |
| Summary: | Adapter %s was exchanged (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10641: Firmware upload started
| Severity: | INFORMATIONAL |
| Description: | Firmware upload started. |
| Summary: | Adapter %s: Firmware upload started (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10642: Firmware upload is executing
| Severity: | INFORMATIONAL |
| Description: | Firmware upload is executing. |
| Summary: | Adapter %s: Firmware upload is executing (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10643: Save configuration
| Severity: | INFORMATIONAL |
| Description: | Save configuration. |
| Summary: | Adapter %s: Save configuration (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10644: Arrays created
| Severity: | INFORMATIONAL |
| Description: | Arrays created. |
| Summary: | Adapter %s: Arrays %s created (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10645: Arrays deleted
| Severity: | INFORMATIONAL |
| Description: | Arrays deleted. |
| Summary: | Adapter %s: Arrays %s deleted (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10646: Trace mode changed
| Severity: | INFORMATIONAL |
| Description: | Trace mode changed. |
| Summary: | Adapter %s: Trace mode changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10647: Panic dump data deleted
| Severity: | INFORMATIONAL |
| Description: | Panic dump data deleted. |
| Summary: | Adapter %s: Panic dump data deleted (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10648: Panic forced
| Severity: | INFORMATIONAL |
| Description: | Panic forced. |
| Summary: | Adapter %s: Panic forced (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10649: Startup script set
| Severity: | INFORMATIONAL |
| Description: | Startup script set. |
| Summary: | Adapter %s: Startup script set (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10650: EXBIOS parameter changed
| Severity: | INFORMATIONAL |
| Description: | EXBIOS parameter changed. |
| Summary: | Adapter %s: EXBIOS parameter changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10651: Auto offline recovery mode changed
| Severity: | INFORMATIONAL |
| Description: | Auto offline recovery mode changed. |
| Summary: | Adapter %s: Auto offline recovery mode changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10652: Clock time changed
| Severity: | INFORMATIONAL |
| Description: | Clock time changed. |
| Summary: | Adapter %s: Clock time changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10653: Factory shipment settings restored
| Severity: | INFORMATIONAL |
| Description: | Factory shipment settings restored. |
| Summary: | Adapter %s: Factory shipment settings restored (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10654: Internal log cleared
| Severity: | INFORMATIONAL |
| Description: | Internal log cleared. |
| Summary: | Adapter %s: Internal log cleared (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10655: NVRAM log cleared
| Severity: | INFORMATIONAL |
| Description: | NVRAM log cleared. |
| Summary: | Adapter %s: NVRAM log cleared (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10656: Unique key refreshed
| Severity: | INFORMATIONAL |
| Description: | Unique key refreshed. |
| Summary: | Adapter %s: Unique key refreshed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10657: Write check parameter changed
| Severity: | INFORMATIONAL |
| Description: | Write check parameter changed. |
| Summary: | Adapter %s: Write check parameter changed (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10659: New firmware version detected
| Severity: | INFORMATIONAL |
| Description: | New firmware version detected. |
| Summary: | Adapter %s: New firmware version %s detected (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10664: Bad block table expansion area initialized
| Severity: | INFORMATIONAL |
| Description: | Bad block table expansion area initialized. |
| Summary: | Adapter %s: Bad block table expansion area initialized (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on logical drive.
Proceed with the following steps:
|
| go to top | |
10665: Bad block table expansion area initialization failed
| Severity: | INFORMATIONAL |
| Description: | Bad block table expansion area initialization failed. |
| Summary: | Adapter %s: Bad block table expansion area initialization failed (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on logical drive.
Proceed with the following steps:
|
| go to top | |
10666: Disk error detected by write data on logical drive during redundant copy
| Severity: | INFORMATIONAL |
| Description: | Disk error detected by write data on logical drive during redundant copy. |
| Summary: | Adapter %s: Disk error detected by write data on logical drive %s during redundant copy (Server %s) |
| Resolution: | A large number of uncorrectable bad blocks were detected on logical drive.
Proceed with the following steps:
|
| go to top | |
10668: Multiple failure recovery on disk successful
| Severity: | INFORMATIONAL |
| Description: | Multiple failure recovery on disk successful. |
| Summary: | Adapter %s: Multiple failure recovery on disk (%s) successful (Server %s) |
| Resolution: | For information only. |
| go to top | |
10669: Hot spare available
| Severity: | INFORMATIONAL |
| Description: | Hot spare available. |
| Summary: | Adapter %s: Hot spare available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10670: Patrol Read (one cycle) started on disk
| Severity: | INFORMATIONAL |
| Description: | Patrol Read (one cycle) started on disk. |
| Summary: | Adapter %s: Patrol Read (one cycle) started on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10671: Patrol Read (one cycle) finished on disk
| Severity: | INFORMATIONAL |
| Description: | Patrol Read (one cycle) finished on disk. |
| Summary: | Adapter %s: Patrol Read (one cycle) finished on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10673: Error recovered on disk
| Severity: | INFORMATIONAL |
| Description: | Error recovered on disk. |
| Summary: | Adapter %s: Error recovered on disk (%s), %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10674: Media error recovered on disk by reassigning new block
| Severity: | INFORMATIONAL |
| Description: | Media error recovered on disk by reassigning new block. |
| Summary: | Adapter %s: Media error recovered on disk (%s) by reassigning new block (Server %s) |
| Resolution: | For information only. |
| go to top | |
10676: Disk increased by cold swap
| Severity: | INFORMATIONAL |
| Description: | Disk increased by cold swap. |
| Summary: | Adapter %s: Disk increased by cold swap on port %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10677: Disk decreased by cold swap
| Severity: | INFORMATIONAL |
| Description: | Disk decreased by cold swap. |
| Summary: | Adapter %s: Disk decreased by cold swap on port %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10678: Disk exchanged by cold swap
| Severity: | INFORMATIONAL |
| Description: | Disk exchanged by cold swap. |
| Summary: | Adapter %s: Disk exchanged by cold swap on port %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10679: SAS interface rate changed
| Severity: | INFORMATIONAL |
| Description: | SAS interface rate changed. |
| Summary: | Adapter %s: SAS interface rate changed on port %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10681: Copyback started on disk
| Severity: | INFORMATIONAL |
| Description: | Copyback started on disk. |
| Summary: | Adapter %s: Copyback started on disk (%s) (Server %s) |
| Resolution: | Check the driver version. |
| go to top | |
10683: Copyback complete on disk
| Severity: | INFORMATIONAL |
| Description: | Copyback complete on disk. |
| Summary: | Adapter %s: Copyback complete on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10690: Operation to mark disk offline (redundant copy) started
| Severity: | INFORMATIONAL |
| Description: | Operation to mark disk offline (redundant copy) started. |
| Summary: | Adapter %s: Operation to mark disk (%s) offline (redundant copy) started (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10691: RAID migration registered for logical drive
| Severity: | INFORMATIONAL |
| Description: | RAID migration registered for logical drive. |
| Summary: | Adapter %s: RAID migration registered for logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10692: MDC aborted by user on logical drive
| Severity: | INFORMATIONAL |
| Description: | MDC aborted by user on logical drive. |
| Summary: | Adapter %s: MDC aborted by user on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10693: Alarm set
| Severity: | INFORMATIONAL |
| Description: | Alarm set. |
| Summary: | Adapter %s: Alarm set (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected disk.
- Replace affected backplane or the data cable.
|
| go to top | |
10698: Background recovery of logical drive could not be started due to bad block table overflow
| Severity: | INFORMATIONAL |
| Description: | Background recovery of logical drive could not be started due to bad block table overflow. |
| Summary: | Adapter %s: Background recovery of logical drive %s could not be started due to bad block table overflow (Server %s) |
| Resolution: | Check the array configuration. |
| go to top | |
10699: New hot spare detected
| Severity: | INFORMATIONAL |
| Description: | New hot spare detected. |
| Summary: | Adapter %s: New hot spare (%s) detected (Server %s) |
| Resolution: | Check the array configuration. |
| go to top | |
10706: Reset received
| Severity: | INFORMATIONAL |
| Description: | Reset received. |
| Summary: | Adapter %s: Reset received (Server %s) |
| Resolution: | Check the driver and firmware version. |
| go to top | |
10707: Operation to mark disk offline started
| Severity: | INFORMATIONAL |
| Description: | Operation to mark disk offline started. |
| Summary: | Adapter %s: Operation to mark disk (%s) offline started (Server %s) |
| Resolution: | Check the driver and firmware version. |
| go to top | |
10708: Operation to delete arrays started
| Severity: | INFORMATIONAL |
| Description: | Operation to delete arrays started. |
| Summary: | Adapter %s: Operation to delete arrays %s started (Server %s) |
| Resolution: | Check the driver and firmware version. |
| go to top | |
10709: Operation to delete logical drive started
| Severity: | INFORMATIONAL |
| Description: | Operation to delete logical drive started. |
| Summary: | Adapter %s: Operation to delete logical drive %s started (Server %s) |
| Resolution: | Check the driver and firmware version. |
| go to top | |
10710: Operation to delete global hot spare on disk started
| Severity: | INFORMATIONAL |
| Description: | Operation to delete global hot spare on disk started. |
| Summary: | Adapter %s: Operation to delete global hot spare on disk (%s) started (Server %s) |
| Resolution: | Check the driver and firmware version. |
| go to top | |
10719: Ioctl busy
| Severity: | INFORMATIONAL |
| Description: | Ioctl busy. |
| Summary: | Adapter %s: Ioctl busy (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10720: Logical drive number for boot changed
| Severity: | INFORMATIONAL |
| Description: | Logical drive number for boot changed. |
| Summary: | Adapter %s: Logical drive number for boot changed to %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10721: Power state change on disk from active to stopped
| Severity: | INFORMATIONAL |
| Description: | Power state change on disk from active to stopped. |
| Summary: | Adapter %s: Power state change on disk (%s) from active to stopped (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10722: Power state change on disk from stopped to active
| Severity: | INFORMATIONAL |
| Description: | Power state change on disk from stopped to active. |
| Summary: | Adapter %s: Power state change on disk (%s) from stopped to active (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10723: Enclosure element status changed
| Severity: | INFORMATIONAL |
| Description: | Enclosure element status changed. |
| Summary: | Adapter %s: Enclosure %s element (SES code %s) status changed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10724: Firmware upload process finished
| Severity: | INFORMATIONAL |
| Description: | Firmware upload process finished. |
| Summary: | Adapter %s: Firmware upload process finished (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10725: Disk firmware update process started
| Severity: | INFORMATIONAL |
| Description: | Disk firmware update process started. |
| Summary: | Adapter %s: Disk firmware update process started (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10726: Disk firmware update process finished
| Severity: | INFORMATIONAL |
| Description: | Disk firmware update process finished. |
| Summary: | Adapter %s: Disk firmware update process finished (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10727: Difference in time information changed
| Severity: | INFORMATIONAL |
| Description: | Difference in time information changed. |
| Summary: | Adapter %s: Difference in time information changed (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10728: Factory shipment settings initialized
| Severity: | INFORMATIONAL |
| Description: | Factory shipment settings initialized. |
| Summary: | Adapter %s: Factory shipment settings initialized (Server %s) |
| Resolution: | Proceed with the following steps:
- Replace affected RAID controller.
|
| go to top | |
10730: Disk rebuild not possible as HDD/SSD mix is not supported in an array
| Severity: | INFORMATIONAL |
| Description: | Disk rebuild not possible as HDD/SSD mix is not supported in an array. |
| Summary: | Adapter %s: Disk (%s) rebuild not possible as HDD/SSD mix is not supported in an array (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10731: Copyback cannot be started on disk from disk, as HDD/SSD mix is not supported in an array
| Severity: | INFORMATIONAL |
| Description: | Copyback cannot be started on disk from disk as HDD/SSD mix is not supported in an array. |
| Summary: | Adapter %s: Copyback cannot be started on disk (%s) from disk (%s), as HDD/SSD mix is not supported in an array (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual recalibration process (e.g. via ServerView RAID Manager). Note: Do not interrupt the charging process by reboots or shutdowns.
- If problem persists replace BBU.
|
| go to top | |
10733: Task was started
| Severity: | INFORMATIONAL |
| Description: | Task was started. |
| Summary: | Task %s for object %s was started by scheduler (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10735: Bad block table of logical drive cleared
| Severity: | INFORMATIONAL |
| Description: | Bad block table of logical drive cleared. |
| Summary: | Adapter %s: Bad block table of logical drive %s cleared (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10740: Cluster of medium errors corrected for logical drive
| Severity: | INFORMATIONAL |
| Description: | Cluster of medium errors corrected for logical drive. |
| Summary: | Adapter %s: Cluster of medium errors corrected for logical drive %s at %s (on disk %s at %s) (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10741: Host bus rescan requested
| Severity: | INFORMATIONAL |
| Description: | Host bus rescan requested. |
| Summary: | Adapter %s: Host bus rescan requested (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10742: Adapter repurposed and factory defaults restored
| Severity: | INFORMATIONAL |
| Description: | Adapter repurposed and factory defaults restored. |
| Summary: | Adapter %s: Adapter repurposed and factory defaults restored (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10743: Disk security key binding updated
| Severity: | INFORMATIONAL |
| Description: | Disk security key binding updated. |
| Summary: | Adapter %s: Disk security key binding updated (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10744: State change from available to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from available to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from available to copyback (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10745: State change from available to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from available to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from available to JBOD (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10746: State change from failed to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from failed to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from failed to copyback (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10747: State change from failed to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from failed to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from failed to JBOD (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10748: State change from hot spare to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from hot spare to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to copyback (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10749: State change from hot spare to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from hot spare to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from hot spare to JBOD (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10750: State change from rebuilding to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from rebuilding to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to copyback (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10751: State change from rebuilding to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from rebuilding to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from rebuilding to JBOD (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10752: State change from operational to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from operational to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from operational to copyback (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10753: State change from operational to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from operational to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from operational to JBOD (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10754: State change from copyback to available
| Severity: | INFORMATIONAL |
| Description: | State change from copyback to available. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to available (Server %s) |
| Resolution: | Check the error code. Then check the controller settings, scheduler settings and disk/logical drive/BBU status. |
| go to top | |
10756: State change from copyback to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from copyback to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10758: State change from copyback to operational
| Severity: | INFORMATIONAL |
| Description: | State change from copyback to operational. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10759: State change from copyback to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from copyback to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10760: State change from copyback to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from copyback to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10761: State change from copyback to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from copyback to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from copyback to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10762: State change from JBOD to available
| Severity: | INFORMATIONAL |
| Description: | State change from JBOD to available. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10764: State change from JBOD to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from JBOD to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10766: State change from JBOD to operational
| Severity: | INFORMATIONAL |
| Description: | State change from JBOD to operational. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10767: State change from JBOD to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from JBOD to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10768: State change from JBOD to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from JBOD to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10769: State change from JBOD to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from JBOD to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from JBOD to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10770: State change by user from available to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from available to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10771: State change by user from available to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from available to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from available to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10772: State change by user from failed to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from failed to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10773: State change by user from failed to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from failed to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from failed to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10774: State change by user from hot spare to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from hot spare to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10775: State change by user from hot spare to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from hot spare to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from hot spare to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10776: State change by user from rebuilding to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from rebuilding to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10777: State change by user from rebuilding to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from rebuilding to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from rebuilding to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10778: State change by user from operational to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from operational to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10779: State change by user from operational to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from operational to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from operational to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10780: State change by user from copyback to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from copyback to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10782: State change by user from copyback to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from copyback to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10784: State change by user from copyback to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from copyback to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10785: State change by user from copyback to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from copyback to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10786: State change by user from copyback to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from copyback to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10787: State change by user from copyback to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from copyback to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from copyback to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10788: State change by user from JBOD to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from JBOD to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to available (Server %s) |
| Resolution: | For information only. |
| go to top | |
10790: State change by user from JBOD to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from JBOD to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to hot spare (Server %s) |
| Resolution: | For information only. |
| go to top | |
10792: State change by user from JBOD to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from JBOD to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10793: State change by user from JBOD to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from JBOD to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to rebuilding (Server %s) |
| Resolution: | For information only. |
| go to top | |
10794: State change by user from JBOD to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from JBOD to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10795: State change by user from JBOD to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from JBOD to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from JBOD to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10796: State change from offline to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from offline to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from offline to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10797: State change by user from offline to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from offline to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to copyback (Server %s) |
| Resolution: | For information only. |
| go to top | |
10798: State change from offline to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from offline to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from offline to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10799: State change by user from offline to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from offline to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from offline to JBOD (Server %s) |
| Resolution: | For information only. |
| go to top | |
10800: Disk security is in external key management mode
| Severity: | INFORMATIONAL |
| Description: | Disk security is in external key management mode. |
| Summary: | Adapter %s: Disk security is in external key management mode (Server %s) |
| Resolution: | For information only. |
| go to top | |
10802: Disk needs key
| Severity: | INFORMATIONAL |
| Description: | Disk needs key. |
| Summary: | Adapter %s: Disk (%s) needs key to be %s %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10806: COD on disk updated as it was stale
| Severity: | INFORMATIONAL |
| Description: | COD on disk updated as it was stale. |
| Summary: | Adapter %s: COD on disk (%s) updated as it was stale (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10810: Logical drive is ready
| Severity: | INFORMATIONAL |
| Description: | Logical drive is ready. |
| Summary: | Adapter %s: Logical drive %s is ready (Server %s) |
| Resolution: | For information only. |
| go to top | |
10811: Test E-mail was sent successfully
| Severity: | INFORMATIONAL |
| Description: | Test E-mail was sent successfully. |
| Summary: | Test E-mail was sent successfully (Server %s) |
| Resolution: | For information only. |
| go to top | |
10815: Enclosure power supply inserted
| Severity: | INFORMATIONAL |
| Description: | Enclosure power supply inserted. |
| Summary: | Adapter %s: Enclosure %s power supply %s inserted (Server %s) |
| Resolution: | For information only. |
| go to top | |
10816: Enclosure power supply turned on
| Severity: | INFORMATIONAL |
| Description: | Enclosure power supply turned on. |
| Summary: | Adapter %s: Enclosure %s power supply %s turned on (Server %s) |
| Resolution: | For information only. |
| go to top | |
10821: Power state change on disk from active to transition
| Severity: | INFORMATIONAL |
| Description: | Power state change on disk from active to transition. |
| Summary: | Adapter %s: Power state change on disk (%s) from active to transition (Server %s) |
| Resolution: | Proceed with the following steps:
- Check installation of all air flow channels, closed housing, and unblocked louvers.
- Check environmental temperature.
|
| go to top | |
10823: Power state change on disk from stopped to transition
| Severity: | INFORMATIONAL |
| Description: | Power state change on disk from stopped to transition. |
| Summary: | Adapter %s: Power state change on disk (%s) from stopped to transition (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10825: Power state change on disk from transition to active
| Severity: | INFORMATIONAL |
| Description: | Power state change on disk from transition to active. |
| Summary: | Adapter %s: Power state change on disk (%s) from transition to active (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10827: Power state change on disk from transition to stopped
| Severity: | INFORMATIONAL |
| Description: | Power state change on disk from transition to stopped. |
| Summary: | Adapter %s: Power state change on disk (%s) from transition to stopped (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10830: Enclosure temperature sensor temperature increase detected
| Severity: | INFORMATIONAL |
| Description: | Enclosure temperature sensor temperature increase detected. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s temperature increase detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10831: Enclosure temperature sensor temperature drop detected
| Severity: | INFORMATIONAL |
| Description: | Enclosure temperature sensor temperature drop detected. |
| Summary: | Adapter %s: Enclosure %s temperature sensor %s temperature drop detected (Server %s) |
| Resolution: | For information only. |
| go to top | |
10832: Enclosure fan speed changed to low
| Severity: | INFORMATIONAL |
| Description: | Enclosure fan speed changed to low. |
| Summary: | Adapter %s: Enclosure %s fan %s speed changed to low (Server %s) |
| Resolution: | For information only. |
| go to top | |
10833: Enclosure fan speed changed to medium
| Severity: | INFORMATIONAL |
| Description: | Enclosure fan speed changed to medium. |
| Summary: | Adapter %s: Enclosure %s fan %s speed changed to medium (Server %s) |
| Resolution: | For information only. |
| go to top | |
10834: Enclosure fan speed changed to high
| Severity: | INFORMATIONAL |
| Description: | Enclosure fan speed changed to high. |
| Summary: | Adapter %s: Enclosure %s fan %s speed changed to high (Server %s) |
| Resolution: | For information only. |
| go to top | |
10835: Disk will be set offline due to SAS/SATA interface error rate too high
| Severity: | INFORMATIONAL |
| Description: | Disk will be set offline due to SAS/SATA interface error rate too high. |
| Summary: | Adapter %s: Disk (%s) will be set offline due to SAS/SATA interface error rate too high (Server %s) |
| Resolution: | For information only. |
| go to top | |
10836: Write cache on disk enabled
| Severity: | INFORMATIONAL |
| Description: | Write cache on disk enabled. |
| Summary: | Adapter %s: Write cache on disk (%s) enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10837: Write cache on disk disabled
| Severity: | INFORMATIONAL |
| Description: | Write cache on disk disabled. |
| Summary: | Adapter %s: Write cache on disk (%s) disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10838: Native Command Queuing on disk enabled
| Severity: | INFORMATIONAL |
| Description: | Native Command Queuing on disk enabled. |
| Summary: | Adapter %s: Native Command Queuing (NCQ) on disk (%s) enabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10839: Native Command Queuing on disk disabled
| Severity: | INFORMATIONAL |
| Description: | Native Command Queuing on disk disabled. |
| Summary: | Adapter %s: Native Command Queuing (NCQ) on disk (%s) disabled (Server %s) |
| Resolution: | For information only. |
| go to top | |
10840: Automatic rebuild will use hot spares
| Severity: | INFORMATIONAL |
| Description: | Automatic rebuild will use hot spares. |
| Summary: | Adapter %s: Automatic rebuild will use hot spares (Server %s) |
| Resolution: | For information only. |
| go to top | |
10841: Automatic rebuild will use available disks and hot spares
| Severity: | INFORMATIONAL |
| Description: | Automatic rebuild will use available disks and hot spares. |
| Summary: | Adapter %s: Automatic rebuild will use available disks and hot spares (Server %s) |
| Resolution: | For information only. |
| go to top | |
10842: Patrol Read rate changed
| Severity: | INFORMATIONAL |
| Description: | Patrol Read rate changed. |
| Summary: | Adapter %s: Patrol Read rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10843: Migration rate changed
| Severity: | INFORMATIONAL |
| Description: | Migration rate changed. |
| Summary: | Adapter %s: Migration rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10844: Initialization rate changed
| Severity: | INFORMATIONAL |
| Description: | Initialization rate changed. |
| Summary: | Adapter %s: Initialization rate changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10845: Consistency check resumed on logical drive
| Severity: | INFORMATIONAL |
| Description: | Consistency check resumed on logical drive. |
| Summary: | Adapter %s: Consistency check resumed on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10847: Initialization suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Initialization suspended on logical drive. |
| Summary: | Adapter %s: Initialization suspended on logical drive %s (Server %s) |
| Resolution: | Initiate manual MDC to initialize the logical drive. |
| go to top | |
10848: Initialization resumed on logical drive
| Severity: | INFORMATIONAL |
| Description: | Initialization resumed on logical drive. |
| Summary: | Adapter %s: Initialization resumed on logical drive %s (Server %s) |
| Resolution: | Initiate manual MDC to initialize the logical drive. |
| go to top | |
10849: Logical drive is used for CacheCade
| Severity: | INFORMATIONAL |
| Description: | Logical drive is used for CacheCade. |
| Summary: | Adapter %s: Logical drive %s is used for CacheCade with capacity %s MB (Server %s) |
| Resolution: | Initiate manual MDC to initialize the logical drive. |
| go to top | |
10850: Logical drive is using CacheCade
| Severity: | INFORMATIONAL |
| Description: | Logical drive is using CacheCade. |
| Summary: | Adapter %s: Logical drive %s is using CacheCade %s (Server %s) |
| Resolution: | Initiate manual MDC to initialize the logical drive. |
| go to top | |
10851: Logical drive is no longer using CacheCade
| Severity: | INFORMATIONAL |
| Description: | Logical drive is no longer using CacheCade. |
| Summary: | Adapter %s: Logical drive %s is no longer using CacheCade %s (Server %s) |
| Resolution: | Initiate manual MDC to initialize the logical drive. |
| go to top | |
10854: MegaRAID Advanced Software Options key applied
| Severity: | INFORMATIONAL |
| Description: | MegaRAID Advanced Software Options key applied. |
| Summary: | Adapter %s: MegaRAID Advanced Software Options (%s) key applied (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual relearn cycle.
- If problem persists replace BBU.
|
| go to top | |
10855: MegaRAID Advanced Software Options key transferred
| Severity: | INFORMATIONAL |
| Description: | MegaRAID Advanced Software Options key transferred. |
| Summary: | Adapter %s: MegaRAID Advanced Software Options (%s) key transferred (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual relearn cycle.
- If problem persists replace BBU.
|
| go to top | |
10856: MegaRAID Advanced Software Options serial number
| Severity: | INFORMATIONAL |
| Description: | MegaRAID Advanced Software Options serial number. |
| Summary: | Adapter %s: MegaRAID Advanced Software Options serial number %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Initiate manual relearn cycle.
- If problem persists replace BBU.
|
| go to top | |
10859: Logical drive power policy changed
| Severity: | INFORMATIONAL |
| Description: | Logical drive power policy changed. |
| Summary: | Adapter %s: Logical drive %s: %s changed (Server %s) |
| Resolution: | BBU capacity is decreased and buffering of data in controller cache is limited. To reach full data retention time replace BBU. |
| go to top | |
10861: Driver is loaded and operational
| Severity: | INFORMATIONAL |
| Description: | Driver is loaded and operational. |
| Summary: | Adapter %s: Driver is loaded and operational (Server %s) |
| Resolution: | For information only. |
| go to top | |
10862: Logical drive mirror broken
| Severity: | INFORMATIONAL |
| Description: | Logical drive mirror broken. |
| Summary: | Adapter %s: Logical drive %s mirror broken (Server %s) |
| Resolution: | For information only. |
| go to top | |
10863: Logical drive mirror joined
| Severity: | INFORMATIONAL |
| Description: | Logical drive mirror joined. |
| Summary: | Adapter %s: Logical drive %s mirror joined (Server %s) |
| Resolution: | For information only. |
| go to top | |
10865: Disk link restored in SAS wide port
| Severity: | INFORMATIONAL |
| Description: | Disk link restored in SAS wide port. |
| Summary: | Adapter %s: Disk (%s) link %s restored in SAS wide port (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10866: Memory module FRU
| Severity: | INFORMATIONAL |
| Description: | Memory module FRU. |
| Summary: | Adapter %s: Memory module FRU is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Unplug affected disk, wait 30 seconds, reinsert it.
- Check/replace cable between controller and affected disk.
- Check version of RAID controller/iRMC firmware, and BIOS.
- Replace affected disk.
|
| go to top | |
10872: Diagnostics passed for disk
| Severity: | INFORMATIONAL |
| Description: | Diagnostics passed for disk. |
| Summary: | Adapter %s: Diagnostics passed for disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10874: Server power capability diagnostic test started
| Severity: | INFORMATIONAL |
| Description: | Server power capability diagnostic test started. |
| Summary: | Adapter %s: Server power capability diagnostic test started (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10875: Disk cache settings enabled during rebuild for disk
| Severity: | INFORMATIONAL |
| Description: | Disk cache settings enabled during rebuild for disk. |
| Summary: | Adapter %s: Disk cache settings enabled during rebuild for disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10876: Disk cache settings restored after rebuild for disk
| Severity: | INFORMATIONAL |
| Description: | Disk cache settings restored after rebuild for disk. |
| Summary: | Adapter %s: Disk cache settings restored after rebuild for disk (%s) (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10877: Disk commissioned as emergency spare
| Severity: | INFORMATIONAL |
| Description: | Disk commissioned as emergency spare. |
| Summary: | Adapter %s: Disk (%s) commissioned as emergency spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10879: BGI suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | BGI suspended on logical drive. |
| Summary: | Adapter %s: BGI suspended on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10880: BGI resumed on logical drive
| Severity: | INFORMATIONAL |
| Description: | BGI resumed on logical drive. |
| Summary: | Adapter %s: BGI resumed on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10881: Migration suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Migration suspended on logical drive. |
| Summary: | Adapter %s: Migration suspended on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10882: Copyback suspended on disk
| Severity: | INFORMATIONAL |
| Description: | Copyback suspended on disk. |
| Summary: | Adapter %s: Copyback suspended on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10883: Reminder: MDC suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Reminder: MDC suspended on logical drive. |
| Summary: | Adapter %s: Reminder: MDC suspended on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10884: Reminder: BGI suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Reminder: BGI suspended on logical drive. |
| Summary: | Adapter %s: Reminder: BGI suspended on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10885: Reminder: Migration suspended on logical drive
| Severity: | INFORMATIONAL |
| Description: | Reminder: Migration suspended on logical drive. |
| Summary: | Adapter %s: Reminder: Migration suspended on logical drive %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10886: Reminder: Rebuild suspended on disk
| Severity: | INFORMATIONAL |
| Description: | Reminder: Rebuild suspended on disk. |
| Summary: | Adapter %s: Reminder: Rebuild suspended on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10887: Reminder: Copyback suspended on disk
| Severity: | INFORMATIONAL |
| Description: | Reminder: Copyback suspended on disk. |
| Summary: | Adapter %s: Reminder: Copyback suspended on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10888: Reminder: Patrol Read suspended
| Severity: | INFORMATIONAL |
| Description: | Reminder: Patrol Read suspended. |
| Summary: | Adapter %s: Reminder: Patrol Read suspended (Server %s) |
| Resolution: | For information only. |
| go to top | |
10889: Erase aborted on disk
| Severity: | INFORMATIONAL |
| Description: | Erase aborted on disk. |
| Summary: | Adapter %s: Erase aborted on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10891: Erase progress on disk
| Severity: | INFORMATIONAL |
| Description: | Erase progress on disk. |
| Summary: | Adapter %s: Erase progress on disk (%s) is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10892: Erase started on disk
| Severity: | INFORMATIONAL |
| Description: | Erase started on disk. |
| Summary: | Adapter %s: Erase started on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10893: Erase finished on disk
| Severity: | INFORMATIONAL |
| Description: | Erase finished on disk. |
| Summary: | Adapter %s: Erase finished on disk (%s) (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10894: Erase aborted on logical drive
| Severity: | INFORMATIONAL |
| Description: | Erase aborted on logical drive. |
| Summary: | Adapter %s: Erase aborted on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10896: Erase progress on logical drive
| Severity: | INFORMATIONAL |
| Description: | Erase progress on logical drive. |
| Summary: | Adapter %s: Erase progress on logical drive %s is %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10897: Erase started on logical drive
| Severity: | INFORMATIONAL |
| Description: | Erase started on logical drive. |
| Summary: | Adapter %s: Erase started on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10898: Erase finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | Erase finished on logical drive. |
| Summary: | Adapter %s: Erase finished on logical drive %s (Server %s) |
| Resolution: | Proceed with the following steps:
- Call your local Fujitsu Helpdesk.
|
| go to top | |
10901: FBU firmware update finished
| Severity: | INFORMATIONAL |
| Description: | FBU firmware update finished. |
| Summary: | Adapter %s: FBU firmware update finished (Server %s) |
| Resolution: | Bring system back to normal operating temperature. |
| go to top | |
10904: CacheCade disassociate started on logical drive
| Severity: | INFORMATIONAL |
| Description: | CacheCade disassociate started on logical drive. |
| Summary: | Adapter %s: CacheCade disassociate started on logical drive %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10905: CacheCade disassociate finished on logical drive
| Severity: | INFORMATIONAL |
| Description: | CacheCade disassociate finished on logical drive. |
| Summary: | Adapter %s: CacheCade disassociate finished on logical drive %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10907: CacheCade disassociate progress on logical drive
| Severity: | INFORMATIONAL |
| Description: | CacheCade disassociate progress on logical drive. |
| Summary: | Adapter %s: CacheCade disassociate progress on logical drive %s is %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10908: CacheCade disassociate aborted by user on logical drive
| Severity: | INFORMATIONAL |
| Description: | CacheCade disassociate aborted by user on logical drive. |
| Summary: | Adapter %s: CacheCade disassociate aborted by user on logical drive %s (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10911: Rebuild suspended on disk
| Severity: | INFORMATIONAL |
| Description: | Rebuild suspended on disk. |
| Summary: | Adapter %s: Rebuild suspended on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10912: Rebuild resumed on disk
| Severity: | INFORMATIONAL |
| Description: | Rebuild resumed on disk. |
| Summary: | Adapter %s: Rebuild resumed on disk (%s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
10913: Link speed changed on SAS port and PHY
| Severity: | INFORMATIONAL |
| Description: | Link speed changed on SAS port and PHY. |
| Summary: | Adapter %s: Link speed changed on SAS port %s and PHY %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10915: Logical drive is now accessible
| Severity: | INFORMATIONAL |
| Description: | Logical drive is now accessible. |
| Summary: | Adapter %s: Logical drive %s is now accessible (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10916: Logical drive is using CacheCade
| Severity: | INFORMATIONAL |
| Description: | Logical drive is using CacheCade. |
| Summary: | Adapter %s: Logical drive %s is using CacheCade (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10917: Logical drive is no longer using CacheCade
| Severity: | INFORMATIONAL |
| Description: | Logical drive is no longer using CacheCade. |
| Summary: | Adapter %s: Logical drive %s is no longer using CacheCade (Server %s) |
| Resolution: | Call your local Fujitsu Helpdesk. |
| go to top | |
10920: Additional information for detected disk
| Severity: | INFORMATIONAL |
| Description: | Additional information for detected disk. |
| Summary: | Adapter %s: Additional information for detected disk (%s) - firmware version: %s, serial number %s (Server %s) |
| Note: | Doesn't affect the normal operation of the system, but can lead to degraded performance due to retries. |
| Resolution: | Proceed with the following steps:
- Replace affected disk/backplane/cable at next service.
|
| go to top | |
10921: RAID Manager started
| Severity: | INFORMATIONAL |
| Description: | RAID Manager started. |
| Summary: | RAID Manager started (Server %s) |
| Note: | Doesn't affect the normal operation of the system, but can lead to degraded performance due to retries. |
| Resolution: | Proceed with the following steps:
- Replace affected disk/backplane/cable at next service.
|
| go to top | |
10922: RAID Manager stopped
| Severity: | INFORMATIONAL |
| Description: | RAID Manager stopped. |
| Summary: | RAID Manager stopped (Server %s) |
| Note: | Doesn't affect the normal operation of the system, but can lead to degraded performance due to retries. |
| Resolution: | Proceed with the following steps:
- Replace affected disk/backplane/cable at next service.
|
| go to top | |
10923: State change from shielded to available
| Severity: | INFORMATIONAL |
| Description: | State change from shielded to available. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to available (Server %s) |
| Note: | Doesn't affect the normal operation of the system, but can lead to degraded performance due to retries. |
| Resolution: | Proceed with the following steps:
- Replace affected disk/backplane/cable at next service.
|
| go to top | |
10926: State change from shielded to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change from shielded to hot spare. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10927: State change from shielded to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change from shielded to rebuilding. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to rebuilding (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10928: State change from shielded to operational
| Severity: | INFORMATIONAL |
| Description: | State change from shielded to operational. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to operational (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10929: State change from shielded to copyback
| Severity: | INFORMATIONAL |
| Description: | State change from shielded to copyback. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to copyback (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10930: State change from shielded to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change from shielded to JBOD. |
| Summary: | Adapter %s: State change on disk (%s) from shielded to JBOD (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10940: State change by user from shielded to available
| Severity: | INFORMATIONAL |
| Description: | State change by user from shielded to available. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to available (Server %s) |
| Resolution: | Proceed with the following steps:
- Wait until checking in shielded state is completed.
- Perform action according to upcoming status.
|
| go to top | |
10943: State change by user from shielded to hot spare
| Severity: | INFORMATIONAL |
| Description: | State change by user from shielded to hot spare. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to hot spare (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10944: State change by user from shielded to rebuilding
| Severity: | INFORMATIONAL |
| Description: | State change by user from shielded to rebuilding. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to rebuilding (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10945: State change by user from shielded to operational
| Severity: | INFORMATIONAL |
| Description: | State change by user from shielded to operational. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to operational (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10946: State change by user from shielded to copyback
| Severity: | INFORMATIONAL |
| Description: | State change by user from shielded to copyback. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to copyback (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10947: State change by user from shielded to JBOD
| Severity: | INFORMATIONAL |
| Description: | State change by user from shielded to JBOD. |
| Summary: | Adapter %s: State change by user on disk (%s) from shielded to JBOD (Server %s) |
| Resolution: | Replace affected disk. |
| go to top | |
10980: Adapter normal
| Severity: | INFORMATIONAL |
| Description: | Adapter normal. |
| Summary: | Adapter %s: Adapter normal (Server %s) |
| Resolution: | Formatting to a smaller size will free up reserve. |
| go to top | |
10983: Attached
| Severity: | INFORMATIONAL |
| Description: | Attached. |
| Summary: | Adapter %s: Attached (Server %s) |
| Resolution: | Proceed with the following steps:
- Force detach.
- If problem persists, call your local Fujitsu Helpdesk.
|
| go to top | |
10985: Format of disk changed
| Severity: | INFORMATIONAL |
| Description: | Format of disk changed. |
| Summary: | Adapter %s: Format of disk (%s) changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
10986: File log cleared
| Severity: | INFORMATIONAL |
| Description: | File log cleared. |
| Summary: | File log cleared (Server %s) |
| Resolution: | For information only. |
| go to top | |
10987: Disk will be set offline due to SMART error
| Severity: | INFORMATIONAL |
| Description: | Disk will be set offline due to SMART error. |
| Summary: | Adapter %s: Disk (%s) will be set offline due to SMART error (Server %s) |
| Resolution: | For information only. |
| go to top | |
10988: Disk will be set offline due to too many unexpected sense events
| Severity: | INFORMATIONAL |
| Description: | Disk will be set offline due to too many unexpected sense events. |
| Summary: | Adapter %s: Disk (%s) will be set offline due to too many unexpected sense events (Server %s) |
| Resolution: | For information only. |
| go to top | |
10991: BBU mode selected
| Severity: | INFORMATIONAL |
| Description: | BBU mode selected. |
| Summary: | Adapter %s: BBU mode selected - %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10992: Periodic BBU relearn was missed and rescheduled
| Severity: | INFORMATIONAL |
| Description: | Periodic BBU relearn was missed and rescheduled. |
| Summary: | Adapter %s: Periodic BBU relearn was missed, and rescheduled to %s (Server %s) |
| Resolution: | For information only. |
| go to top | |
10993: Adapter reset requested by host
| Severity: | INFORMATIONAL |
| Description: | Adapter reset requested by host. |
| Summary: | Adapter %s: Adapter reset requested by host (Server %s) |
| Resolution: | For information only. |
| go to top | |
10994: Adapter reset requested by host completed
| Severity: | INFORMATIONAL |
| Description: | Adapter reset requested by host completed. |
| Summary: | Adapter %s: Adapter reset requested by host, completed (Server %s) |
| Resolution: | For information only. |
| go to top | |
11002: Peer adapter has joined high availability domain
| Severity: | INFORMATIONAL |
| Description: | Peer adapter has joined high availability domain. |
| Summary: | Adapter %s: Peer adapter has joined high availability domain (ID: %s) (Server %s) |
| Resolution: | For information only. |
| go to top | |
11004: Disk is managed by peer adapter
| Severity: | INFORMATIONAL |
| Description: | Disk is managed by peer adapter. |
| Summary: | Adapter %s: Disk (%s) is managed by peer adapter (Server %s) |
| Resolution: | For information only. |
| go to top | |
11005: Disk is managed by local adapter
| Severity: | INFORMATIONAL |
| Description: | Disk is managed by local adapter. |
| Summary: | Adapter %s: Disk (%s) is managed by local adapter (Server %s) |
| Resolution: | For information only. |
| go to top | |
11006: Logical drive is managed by peer adapter
| Severity: | INFORMATIONAL |
| Description: | Logical drive is managed by peer adapter. |
| Summary: | Adapter %s: Logical drive %s is managed by peer adapter (Server %s) |
| Resolution: | For information only. |
| go to top | |
11007: Logical drive is managed by local adapter
| Severity: | INFORMATIONAL |
| Description: | Logical drive is managed by local adapter. |
| Summary: | Adapter %s: Logical drive %s is managed by local adapter (Server %s) |
| Resolution: | For information only. |
| go to top | |
11009: Logical drive access is shared
| Severity: | INFORMATIONAL |
| Description: | Logical drive access is shared. |
| Summary: | Adapter %s: Logical drive %s access is shared (Server %s) |
| Resolution: | For information only. |
| go to top | |
11010: Logical drive access is exclusive
| Severity: | INFORMATIONAL |
| Description: | Logical drive access is exclusive. |
| Summary: | Adapter %s: Logical drive %s access is exclusive (Server %s) |
| Resolution: | For information only. |
| go to top | |
11017: High availability cache mirror is online
| Severity: | INFORMATIONAL |
| Description: | High availability cache mirror is online. |
| Summary: | Adapter %s: High availability cache mirror is online (Server %s) |
| Resolution: | For information only. |
| go to top | |
11023: Disk temperature is normal
| Severity: | INFORMATIONAL |
| Description: | Disk temperature is normal. |
| Summary: | Adapter %s: Disk (%s) temperature (%s C) is normal (Server %s) |
| Resolution: | For information only. |
| go to top | |
11025: Disk IOs are normal (no throttling)
| Severity: | INFORMATIONAL |
| Description: | Disk IOs are normal (no throttling). |
| Summary: | Adapter %s: Disk (%s) IOs are normal (no throttling) (Server %s) |
| Resolution: | For information only. |
| go to top | |
11026: Disk has life left
| Severity: | INFORMATIONAL |
| Description: | Disk has life left. |
| Summary: | Adapter %s: Disk (%s) has %s percent life left. Life left thresholds - warning: %s percent, critical: %s percent (Server %s) |
| Resolution: | For information only. |
| go to top | |
11034: Setting logical drive as boot device
| Severity: | INFORMATIONAL |
| Description: | Setting logical drive as boot device. |
| Summary: | Adapter %s: Setting logical drive %s as boot device (Server %s) |
| Resolution: | For information only. |
| go to top | |
11035: Setting disk as boot device
| Severity: | INFORMATIONAL |
| Description: | Setting disk as boot device. |
| Summary: | Adapter %s: Setting disk (%s) as boot device (Server %s) |
| Resolution: | For information only. |
| go to top | |
11036: The BBU temperature is changed
| Severity: | INFORMATIONAL |
| Description: | The BBU temperature is changed. |
| Summary: | Adapter %s: The BBU temperature is changed to %s C (Server %s) |
| Resolution: | For information only. |
| go to top | |
11037: The adapter temperature is changed
| Severity: | INFORMATIONAL |
| Description: | The adapter temperature is changed. |
| Summary: | Adapter %s: The adapter temperature is changed to %s C (Server %s) |
| Resolution: | For information only. |
| go to top | |
11041: Boot device reset
| Severity: | INFORMATIONAL |
| Description: | Boot device reset. |
| Summary: | Adapter %s: Boot device reset, setting target ID as invalid (Server %s) |
| Resolution: | For information only. |
| go to top | |
11044: Power watts usage base IOs throttle started
| Severity: | INFORMATIONAL |
| Description: | Power watts usage base IOs throttle started. |
| Summary: | Adapter %s: Power %s watts usage base IOs throttle started (Server %s) |
| Resolution: | For information only. |
| go to top | |
11045: Power base IOs throttle stopped
| Severity: | INFORMATIONAL |
| Description: | Power base IOs throttle stopped. |
| Summary: | Adapter %s: Power base IOs throttle stopped (Server %s) |
| Resolution: | For information only. |
| go to top | |
11046: Adapter tunable parameters changed
| Severity: | INFORMATIONAL |
| Description: | Adapter tunable parameters changed. |
| Summary: | Adapter %s: Adapter tunable parameter(s) changed (Server %s) |
| Resolution: | For information only. |
| go to top | |
11047: Adapter operating temperature within normal range
| Severity: | INFORMATIONAL |
| Description: | Adapter operating temperature within normal range. |
| Summary: | Adapter %s: Adapter operating temperature within normal range, full operation restored (Server %s) |
| Resolution: | For information only. |
| go to top | |
11051: Connection to host established
| Severity: | INFORMATIONAL |
| Description: | Connection to host established. |
| Summary: | Connection to host %s established (Server %s) |
| Resolution: | For information only. |
| go to top | |
11052: Adapter supports high availability mode currently functioning with high availability feature set
| Severity: | INFORMATIONAL |
| Description: | Adapter supports high availability mode currently functioning with high availability feature set. |
| Summary: | Adapter %s: Adapter supports high availability mode, currently functioning with high availability feature set (Server %s) |
| Resolution: | For information only. |
| go to top | |
11053: Adapter supports high availability mode currently functioning with single adapter feature set
| Severity: | INFORMATIONAL |
| Description: | Adapter supports high availability mode currently functioning with single adapter feature set. |
| Summary: | Adapter %s: Adapter supports high availability mode, currently functioning with single adapter feature set (Server %s) |
| Resolution: | For information only. |
| go to top | |
11055: Adapter has entered maintenance mode
| Severity: | INFORMATIONAL |
| Description: | Adapter has entered maintenance mode. |
| Summary: | Adapter %s: Adapter has entered maintenance mode (Server %s) |
| Resolution: | For information only. |
| go to top | |
11056: Adapter has returned to normal mode
| Severity: | INFORMATIONAL |
| Description: | Adapter has returned to normal mode. |
| Summary: | Adapter %s: Adapter has returned to normal mode (Server %s) |
| Resolution: | For information only. |
| go to top | |
11057: Topology is in mode
| Severity: | INFORMATIONAL |
| Description: | Topology is in mode. |
| Summary: | Adapter %s: Topology is in %s mode (Server %s) |
| Resolution: | For information only. |
| go to top | |